We stopped shipping 'temporary' email digests without unsubscribe — deliverability dies and members lose trust measurably always. In engineering pitfalls (thread 11): The quiet win was documenting which Slack channel is authoritative during incidents. The mentor who said 'sleep, then ship' was annoying and correct.

We learned that customers forgive slow fixes if communication is honest and frequent. In engineering pitfalls (thread 11): We learned that customers trust companies that admit mistakes in public status updates quickly. We stopped confusing roadmap slides with committed engineering capacity reality.

The best teams celebrate learning from failed experiments without shame spirals. In engineering pitfalls (thread 11): We learned that customers trust changelog honesty more than marketing superlatives. The mentor who said 'tell me the rollback plan in one paragraph' improved migration quality.

We stopped confusing 'more circles' with 'healthier network' when measuring product success honestly quarterly. In engineering pitfalls (thread 11): We stopped treating 'tech debt' as a guilt word and started tagging themes with business outcomes quarterly. The integration that validated webhook signatures stopped a replay scare cold.

We learned that transparent pricing for paid circles beats hidden surcharges when hosts compare platforms quarterly helpfully finally always. In engineering pitfalls (thread 11): The mentor who said 'show me the reply latency distribution' grounded reliability debates for discussion products helpfully. Sometimes the right answer is fewer features and clearer defaults.

We learned that humour about standups lands when it proposes a concrete experiment to shorten them next week. In engineering pitfalls (thread 11): We learned that writing for your future self is an act of compassion. The architecture spike that listed kill criteria prevented sunk cost attachment early.

We learned that customers notice when performance improvements ship without fanfare — they feel it. In engineering pitfalls (thread 11): The mentor who said 'show me the reply latency distribution' grounded reliability debates for discussion products helpfully. The mentor who said 'measure twice, cut once' applied to migrations too literally.

The quiet win was aligning on a single on-call escalation policy across product and infra. In engineering pitfalls (thread 11): We learned that customers appreciate when you sunset features with timelines and export paths. The flaky chaos experiment that only ran manually never found issues until we automated monthly runs.

We stopped shipping dashboards without a named consumer for each chart. In engineering pitfalls (thread 11): The mentor who said 'prove funnel conversion with experiments' sharpened growth marketing debates usefully. We should have deleted unused DNS CNAME chains pointing at deprecated marketing pages — drift hurts SEO too.

The vendor integration succeeded when we owned retries, not when we blamed latency. In engineering pitfalls (thread 11): The smallest type annotation prevented a class of null surprises — types as docs. The mentor who said 'show me the leading indicator chart' sharpened growth debates measurably again.

We learned that empathy for users and empathy for teammates are the same skill. In engineering pitfalls (thread 11): The 'obvious' security control was missing because two teams thought the other owned it. We learned that transparent incident timelines reduce conspiracy theories internally too.

We should have invested in synthetic checks for the login path specifically. In engineering pitfalls (thread 11): The quiet win was documenting which alerts wake humans vs only tickets. We stopped confusing 'busy' engineers with 'fully utilised' capacity for planning.

We learned that customers trust companies that admit mistakes in public status updates quickly. In engineering pitfalls (thread 11): We learned that naming a risk does not summon it — silence does not protect you. The integration that validated idempotency on refunds prevented double-credit incidents quietly.

Naming things poorly cost us more sprint time than any algorithm choice. In engineering pitfalls (thread 11): We learned that customers trust changelog honesty about security fixes more than silent patching ever could. The integration that surfaced partial batch failures prevented silent under-billing in invoicing quietly.

The architecture diagram updated monthly beat the one updated once at kickoff. In engineering pitfalls (thread 11): The right default in config beats a thousand-page admin guide nobody reads. The retrospective action items without owners were wishes, not work.