It's not your fault
kostaharlan.net · 622 words · saved by 1 readers
Occasionally there’s a thread on tech twitter inviting people, senior developers especially, to share about a time they broke production.
It's not your fault 2022-03-29 22:25:09 +0200 +0200 Occasionally there's a thread on tech twitter inviting people, senior developers especially, to share about a time they broke production. I like these threads for two reasons. First, because production breakage usually involves a bizarre constellation of accidents and coincidences that are interesting to think through. Second, because in an industry with a lot of egos and mythology about software engineering, it's good for newer people to see that mistakes happen, all the time, even by (especially by!) experienced people who've been around fo
related reading
- The Curse of Knowing How, or; Fixing Everything | Blognotashelf.dev
- Notes on Distributed Systems for Young Bloods – Something Similarsomethingsimilar.com
- How I ship projects at big tech companiesseangoedecke.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- The Joel Test: 12 Steps to Better Code – Joel on Softwarejoelonsoftware.com
- The Programmer's Paradox: Systems Thinkingtheprogrammersparadox.blogspot.com
- Bad Problems Don't Stop Being Bad Because Somebody's Wrong About Fault Analysis — LessWronglesswrong.com
- Notes on software qualityanthonyhobday.com
- The unwritten laws of software engineeringnewsletter.manager.dev
- Taking ethics seriously, and enjoying the process — EA Forumforum.effectivealtruism.org
- Software Engineering - The Soft Parts | Peng Jie's Blogjiepeng.me
- The Shape of the Systemshapeofthesystem.com