Lazy Engineering
summary
Argues that deliberate laziness — four principles: question requirements, keep it simple, do fewer things at once, and write things down — lets teams avoid weeks of unnecessary work. Gives a concrete shortcut: instead of building a daily MailChimp sync service, ship a modal plus a CSV export tweak so users import via MailChimp’s CSV importer, get real usage feedback, then decide whether to invest in the full integration. Recommends small PRs, delaying tech decisions (no DB until needed) and using infra-as-code and notes to remove mental load.
AI-written summary · about
chapters (5)
related talks
24mExpediency & Fluency
31mThe Effective Developer - Work Smarter, Not Harder
27mStop overthinking and go create things
36m"Engineering to embrace change" Or "How clumsy engineering can lead to powerful research – Part II"
38mSimplicity: The Key to Software Success
05mEngineering Without Dogma: When to Ignore the Best Practices
26mHacks to Work More Efficiently- Rain Leander
28mHow to prioritize dev experience in the development process