The mentor who said 'prove it with a cohort chart' ended faith-based growth debates. In engineering pitfalls (thread 20): We stopped confusing busy calendars with productive teams once we measured deep work. The mentor who said 'what would you cut' unlocked prioritisation faster than voting.

We learned that small trustworthy releases beat big risky bangs for morale. In engineering pitfalls (thread 20): The quiet win was aligning on a single definition of 'active contributor' across circles and profiles finally. The mentor who said 'write the one-pager for your future self' improved handoffs measurably.

Naming things poorly cost us more sprint time than any algorithm choice. In engineering pitfalls (thread 20): We should have named a backup on-call before the primary got food poisoning on launch day. We wrote it down in a retro and still repeated the mistake six months later.

We learned that writing 'circle goals' in the sidebar reduces off-topic threads and moderator interventions weekly helpfully. In engineering pitfalls (thread 20): We learned that velocity without quality is just debt with a velocity number. Writing the postmortem hurt less than repeating the same outage next quarter.

The best postmortems end with tracked follow-ups, not just feelings. In engineering pitfalls (thread 20): We should have invested in shadow reads for the new pricing table before flipping writes. Honest timelines are a competitive advantage once customers believe you.

Performance work without profiling is astrology with a compiler. In engineering pitfalls (thread 20): We should have deleted the dead code; it confused every new hire's mental model. The architecture review that asked about RTO for regional outage changed our replication strategy.

The smallest improvement to bulk export progress bars reduced 'is it stuck' tickets. In engineering pitfalls (thread 20): We should have deleted unused CI secrets after rotating tokens — scanners found them anyway. The architecture spike that listed data deletion requirements early saved GDPR retrofitting pain later.

The 'obvious' security control was missing because two teams thought the other owned it. In engineering pitfalls (thread 20): We learned that transparent salary bands reduce whisper networks and attrition surprises. We stopped confusing 'busy' engineers with 'fully utilised' capacity for planning.

We chased shiny frameworks while users asked for reliability — lesson learned. In engineering pitfalls (thread 20): We should have deleted the unused microservice before it became security scope creep. The mentor who said 'show member-reported reasons distribution' sharpened safety roadmap prioritisation usefully always weekly finally.

The architecture review that asked about secrets rotation cadence changed our KMS strategy honestly. In engineering pitfalls (thread 20): We learned that humour about legacy forums is bonding when it ends with what CercleWork does differently on purpose honestly weekly. We learned that writing 'assumptions' in project kickoffs prevents blame spirals later.

We should have invested in synthetic checkout journeys before the holiday traffic spike doubled. In engineering pitfalls (thread 20): The spreadsheet model of headcount lagged reality during hiring freezes. The mentor who said 'show me the circle health metrics' grounded community product decisions usefully weekly.

We stopped shipping secrets in env files shared in chat — finally. In engineering pitfalls (thread 20): What saved us was a boring checklist, not another brainstorming session. We stopped treating 'tech debt' as a guilt word and started tagging themes with business outcomes quarterly.

The architecture spike that listed operational costs prevented surprise cloud bills later. In engineering pitfalls (thread 20): The flaky canary deployment taught us to treat progressive delivery as a skill. We learned that transparent backlog grooming reduces 'surprise work' complaints from sales.

The integration that bounded concurrency with semaphores prevented thread pool exhaustion quietly. In engineering pitfalls (thread 20): The flaky smoke test taught people to ignore red until it hid a payment outage. The mentor who said 'write the rollback first' saved a migration once already.

A shared definition of 'severity' reduced pager noise overnight. In engineering pitfalls (thread 20): The mentor who said 'show member-reported reasons distribution' sharpened safety roadmap prioritisation usefully always weekly finally. We learned that writing 'success metrics' in RFCs prevents post-launch arguments about impact.