This talk is about working in the open in your day-to-day in a development team. Sharing early - whether it’s a rough idea, a half-written doc, or a messy prototype - can lead to fast feedback from people you might not expect, useful conversations, and even collaborators. We know the value of sharing early versions of products with customers to get feedback: we should bring that same spirit to our day-to-day technical work, too.
Have you ever crafted a detailed answer to a teammate's question and then buried it in your chat history? Or kept some half-baked solution thoughts to yourself only to discover that someone else has spent ages getting to the same result? We’ll look at how to make your work-in-progress visible to others without causing confusion, and why it’s worth the risk of looking stupid!
Follow-up links:
- Robin Sloane / Andy Matuschak: https://notes.andymatuschak.org/About_these_notes?stackedNotes=z21cgR9K3UcQ5a7yPsj2RUim3oM2TzdBByZu
- Cult of Done Manifesto: https://medium.com/@bre/the-cult-of-done-manifesto-724ca1c2ff13
- Clare Sudbery: Let's stop making each other feel stupid: https://insimpleterms.blog/lets-stop-making-each-other-feel-stupid
- `just` command runner: https://just.systems
- Tech radar talk at LeadDev 2024: Andra Blaj: https://leaddev.com/technical-direction/how-to-use-technology-radars-to-make-transparent-tech-decisions
- Thoughtworks tech radar: https://www.thoughtworks.com/radar/faq
- AOE's tech radar tool: https://github.com/AOEpeople/aoe_technology_radar