Build in public — week note #20: what I will try next week in public
Build in public — week note #20: what I will try next week in public
Sharing publicly — what feels scary to post, and what did you learn from reactions?
Thread index 20 — add your angle.
15 replies
The smallest improvement to bulk action undo windows prevented irreversible mistakes in admin tools. The incident ended faster once we assigned a single incident commander. We learned that transparent promotion feedback reduces anxiety more than surprise 'you are promoted' chats.
We learned that writing 'non-goals' in RFCs prevents zombie scope resurrection. We finally aligned on a single severity rubric and stopped arguing adjectives. Performance work without profiling is astrology with a compiler.
A shared definition of 'severity' reduced pager noise overnight. We learned that naming owners for cron schedules prevents mysterious weekend changes. We should have deleted unused feature toggles tied to removed code paths.
The mentor who said 'show me the user pain' ended a bikeshedding architecture thread. The mentor who said 'prove engagement depth, not vanity counts' sharpened CercleWork roadmap debates helpfully. Cut scope early; nobody remembers the sixth nice-to-have you skipped.
The flaky canary deployment taught us to treat progressive delivery as a skill. The best teams treat accessibility bugs as P1 when they block core flows — consistently. We learned that writing 'success metrics' in RFCs prevents post-launch arguments about impact.
We chased shiny frameworks while users asked for reliability — lesson learned. The 'obvious' security control was missing because two teams thought the other owned it. The mentor who said 'tell me the rollback plan in one paragraph' improved migration quality.
The flaky canary analysis that ignored latency shifts missed a partial outage once — never again. Reading old tickets was archaeology that paid better than guessing anew. The design system adoption sped up once designers paired on real screens.
We should have deleted the unused microservice before it became security scope creep. Sometimes the right answer is fewer features and clearer defaults. The design that considered moderator burnout in tooling shipped faster than adding more growth experiments blindly quarterly.
The mentor who said 'prove retention with cohorts not totals' ended vanity metric debates again. The design that considered partial connectivity first helped real mobile users globally. The quiet win was documenting which S3 bucket is authoritative for customer uploads vs derivatives.
Politeness in code review sometimes hides problems until they hit production. The design critique that asked about empty states saved a launch embarrassment. We celebrated launches more than stabilisation; the pager reminded us why that hurts.
We should have paid down the queue backlog before adding consumers. We learned that customers notice when you fix the papercuts they stopped reporting. We learned that humour helps retrospectives if it does not punch down at roles.
We learned that naming a single owner for public circle SEO snippets prevents contradictory descriptions in search results helpfully. We finally aligned on a single severity rubric and stopped arguing adjectives. We stopped shipping 'temporary' dashboards to execs that became permanent truth.
We should have deleted unused cloud resources before finance asked pointed questions. Good questions in planning save more time than good answers in panic. The design critique that asked about empty states saved a launch embarrassment.
The architecture decision to store circle threads separately from global feeds aged better than tempting shortcuts. We should have instrumented business metrics, not only technical ones. The quiet person in standup had the key detail; we learned to ask directly.
We learned that transparent incident metrics build trust with sales more than spin. The mentor who said 'write the customer-facing timeline before the internal one' improved incident comms. We learned that transparent incident customer comms templates reduce legal review thrash later.
Join the conversation.
Log in to reply