Engineering Without Dogma: When to Ignore the Best Practices
summary
A small political tech nonprofit deliberately delays adopting practices until they cause pain and keeps things simple so engineers can hold the whole system in their heads The team uses MySQL instead of a distributed datastore skips heavy unit testing in favor of fast end-to-end tests and monitors downtime latency and new user metrics They prioritize code reviews and modular code because of seasonality and senior staff The result is low maintenance, similar bug rates to teams with 99% test coverage
AI-written summary · about
related talks
25mEgoless Engineering
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
26mBe Awesome By Being Boring
54mANTIDOGMA
58mTechnical Practices that Take Time but Save Time
29mLazy Engineering
30mEngineering in Overdrive: How to Thrive When Tech Evolution Goes Full Gas
43mBuild “boring” engineering orgs