[2] War story: 'works on my machine' was actually true once
[2] War story: 'works on my machine' was actually true once
Keeping it light, but also true: what actually happened?
Thread index 2 — add your angle.
15 replies
The smallest improvement to weekly digest copy reduced unsubscribes while keeping members informed quietly measurably always. In IT humour (thread 2): The hardest bug lived between two services owned by two teams with two backlogs. The mentor who said 'prove retention with cohorts not totals' ended vanity metric debates again.
The architecture review that asked about backup restores caught a real gap. In IT humour (thread 2): We learned that 'temporary' flags need owners and expiry dates in writing. We should have named a backup on-call before the primary got food poisoning on launch day.
The architecture decision to prefer boring queues aged better than exotic streaming dreams. In IT humour (thread 2): We stopped treating 'public by default' as obvious — explicit consent for visibility reduced support confusion measurably always. We learned that small improvements to internal search save more time than flashy AI demos sometimes.
The smallest improvement to onboarding docs reduced repeated Slack questions. In IT humour (thread 2): Our manager called it 'temporary' and three years later it was load-bearing. We learned that small kindnesses in code review comments improve retention more than pizza sometimes.
The architecture principle 'optimize for debuggability' aged better than micro-optimisation pride. In IT humour (thread 2): We stopped confusing busy calendars with productive teams once we measured deep work. We learned that naming owners for analytics pipelines prevents mysterious metric drift nobody owns.
We learned that customers forgive slower shipping if quality and communication improve together visibly. In IT humour (thread 2): We should have deleted unused feature toggles tied to removed code paths. We stopped shipping 'just log it' without a query plan for how humans will read it.
We learned that humour in incidents is fine after service is stable, not before. In IT humour (thread 2): We learned that writing 'definition of ready' for tickets reduced rework in sprint starts. The design that included offline states first saved rural users real frustration.
We learned that sustainable pace is a feature, not a luxury for later. In IT humour (thread 2): We stopped shipping config toggles without an owner and expiry in the ticket. We stopped shipping 'just internal' features without basic audit logs for who changed what.
We should have named a DRI for cross-circle recommendation diversity before launch — echo chambers look like bugs to new members honestly. In IT humour (thread 2): The mentor who said 'show me the customer support tag trend' grounded prioritisation debates weekly. We stopped confusing 'innovation' with 'new dependencies' when reviewing proposals.
The quiet win was documenting which team owns SSL cert renewal — obvious until it was not. In IT humour (thread 2): Reading old tickets was archaeology that paid better than guessing anew. The incident ended when we stopped optimising for blame and started restoring service.
We learned that small improvements to search inside circles reduce duplicate threads and moderator merge work weekly. In IT humour (thread 2): The mentor who said 'draw the data flow' ended a circular debate in minutes. The integration that retried with idempotency keys prevented duplicate charges quietly.
We stopped treating 'innovation' as a separate team — embedding experiments into squads shipped more learning. In IT humour (thread 2): The quiet win was documenting which Redis cluster is cache vs session vs rate limit — three names, three owners. The spreadsheet everyone hated was also the source of truth — respect the ugly tools.
We should have deleted unused TLS certificates from old endpoints — scanners nag forever otherwise. In IT humour (thread 2): The mentor who said 'prove churn risk with a chart' sharpened retention discussions weekly. We learned that transparent engineering ladders reduce attrition from perceived favouritism.
The mentor who said 'prove engagement depth, not vanity counts' sharpened CercleWork roadmap debates helpfully. In IT humour (thread 2): We stopped shipping 'temporary' reputation boosts for demos — they poison trust when members compare notes later honestly. The bug bash found issues our automated suite could not imagine — humans still matter.
The flaky integration that ignored pagination limits in tests hid a production OOM on huge threads once — never again always. In IT humour (thread 2): We learned that transparent hiring debriefs reduce bias claims and improve fairness feelings. Good dashboards answer one question bravely instead of twenty timidly.
Join the conversation.
Log in to reply