Build in public — week note #12: a partnership that almost happened
Build in public — week note #12: a partnership that almost happened
Sharing publicly — what feels scary to post, and what did you learn from reactions?
Thread index 12 — add your angle.
15 replies
We learned that psychological safety includes admitting you need help before deadline day. We should have deleted the feature nobody used; it still cost support time. We learned that small improvements to internal search save more time than flashy AI demos sometimes.
We should have deleted unused CI secrets after rotating tokens — scanners found them anyway. Copy-paste from Stack Overflow without tests is not 'moving fast' — it is gambling. We finally instrumented the queue depth and stopped arguing from vibes.
We stopped confusing motion with progress once we counted outcomes weekly. Staging parity with prod sounds expensive until you price one bad release. We stopped confusing 'innovation' with 'complexity' in engineering interviews.
We stopped optimising for individual hero points and optimised for bus factor. We learned that empathy for users and empathy for teammates are the same skill. What saved us was a boring checklist, not another brainstorming session.
We stopped confusing 'busy sprint' with 'valuable sprint' when reporting to leadership. The flaky test quarantine process without expiry became permanent — process decay is real. A shared definition of 'severity' reduced pager noise overnight.
The integration that validated markdown sanitisation for replies prevented XSS surprises in public circles quietly always. We should have deleted unused DNS CNAME chains pointing at deprecated marketing pages — drift hurts SEO too. The flaky test quarantine process without expiry became permanent — process decay is real.
The design that considered low-bandwidth users for image-heavy threads improved global participation measurably. The mentor who said 'draw the box' saved me from over-engineering for months. Customers remember how you behave during failure more than during success.
We stopped treating on-call as punishment and started rotating knowledge deliberately. The architecture diagram updated monthly beat the one updated once at kickoff. We should have deleted dead feature code before the security review found secrets in it.
The quiet win was aligning on a single definition of 'active user' across teams finally. We learned that customers notice when you ship accessibility improvements without being asked loudly. We stopped shipping 'temporary' dashboards to execs that became permanent truth.
We should have invested in staging data refresh before the compliance audit panic. We learned that psychological safety includes admitting you need help before deadline day. The architecture spike that listed multi-cloud egress costs prevented surprise bills honestly.
Documentation written during onboarding beats documentation written for auditors. We learned that transparent promotion feedback reduces anxiety more than surprise 'you are promoted' chats. The architecture review that asked about cold start SLOs changed our packaging strategy honestly.
The quiet win was documenting which database is authoritative for each entity finally. We should have named a backup on-call before the primary got food poisoning on launch day. We should have deleted unused CI secrets after rotating tokens — scanners found them anyway.
Good leaders protect focus time; calendars are organisational debt too. Customers never saw the clever architecture — they felt the latency and the bugs. We stopped confusing 'busy roadmap' with 'validated roadmap' in planning reviews.
The best teams celebrate learning from failed experiments without shame spirals. The integration that bounded payload sizes prevented a memory incident during uploads. The quiet refactor that removed a thousand lines felt better than adding features.
We should have deleted unused CI secrets after rotating tokens — scanners found them anyway. We learned that writing runbooks during daylight saves panic at night. We learned that transparent engineering hiring loops reduce candidate ghosting and bad offers.
Join the conversation.
Log in to reply