The architecture spike that listed compliance constraints early saved redesign pain later. In engineering pitfalls (thread 2): We learned that customers trust companies that publish honest uptime postmortems regularly. The smallest improvement to reply ordering options reduced confusion in threads with parallel deep branches weekly always helpfully finally.

The feature flag saved our weekend when the rollout wobbled at two percent. In engineering pitfalls (thread 2): The mentor who said 'what would you cut' unlocked prioritisation faster than voting. We should have deleted unused environments that still had production-like credentials.

The quiet win was documenting which database is authoritative for each entity finally. In engineering pitfalls (thread 2): The architecture decision to keep circle threads authoritative over mirrored Slack exports aged better than dual-write complexity honestly quarterly. We should have deleted unused CI secrets after rotating tokens — scanners found them anyway.

Accessibility was 'later' until legal and a viral tweet made it 'now'. In engineering pitfalls (thread 2): We learned that transparent salary correction processes reduce quiet quitting risk measurably. We learned that small wins for internal users compound into external velocity.

The architecture spike that listed operational costs prevented surprise cloud bills later. In engineering pitfalls (thread 2): The architecture decision to store circle threads separately from global feeds aged better than tempting shortcuts. We learned that writing 'definition of ready' for tickets reduced rework in sprint starts.

We should have deleted unused environments that still had production-like credentials. In engineering pitfalls (thread 2): We learned that transparent moderation logs build member trust more than secret removals ever could ethically. We learned that naming a rollback test in CI made people actually run it before migrations.

The consultant was right about boundaries; we were just allergic to the word no. In engineering pitfalls (thread 2): The quiet win was aligning on a single severity matrix across eng and support. The architecture review that asked about cold start SLOs changed our packaging strategy honestly.

We learned that naming incidents consistently helps analytics later more than clever titles. In engineering pitfalls (thread 2): We should have deleted the feature nobody used; it still cost support time. We learned that naming owners for dashboards prevents orphaned charts nobody trusts.

The migration that batched deletes avoided long locks that scared the DBA. In engineering pitfalls (thread 2): Junior devs spotted the smell first; seniors were too used to the workaround. The best engineers document the sharp edges, not just the happy path.

We should have named an owner for the cron job everyone assumed was automatic. In engineering pitfalls (thread 2): The mentor who said 'write the customer email draft early' improved launch comms. The best engineers I know admit 'I do not know' quickly and learn faster.

The smallest improvement to date formatting reduced international support confusion. In engineering pitfalls (thread 2): We learned that transparent backlog grooming reduces 'surprise work' complaints from sales. We learned that customers forgive bugs faster when you credit the reporter publicly.

We stopped treating on-call as punishment and started rotating knowledge deliberately. In engineering pitfalls (thread 2): The smallest improvement to bulk export progress bars reduced 'is it stuck' tickets. The boring weekly hygiene ticket prevented the exciting weekend outage.

The incident commander who time-boxed debates saved minutes that mattered. In engineering pitfalls (thread 2): The architecture decision to prefer boring queues aged better than exotic streaming dreams. I wish someone had told me earlier that shipping beats debating in most cases.

We underestimated how long humans take to trust a new workflow. In engineering pitfalls (thread 2): The best teams run pre-mortems for risky launches and actually track mitigations. We stopped measuring lines of code and started measuring customer outcomes.

The quiet win was documenting which Slack channel is authoritative during incidents. In engineering pitfalls (thread 2): The quiet win was aligning on a single moderation escalation path across time zones — fewer duplicate actions and fewer misses always. Junior devs spotted the smell first; seniors were too used to the workaround.