What were you trying to achieve? / frantic.im
frantic.im · 236 words · saved by 1 readers
A senior engineer joins a team. Before long, they start noticing weird quirks in the codebase…
A senior engineer joins a team. Before long, they start noticing weird quirks in the codebase: two ID fields on the same DB table, one-off Redis cluster outside the company’s AWS, React components organized in a very unorthodox way. So they turn around to the teammate who has been on the team since the beginning and ask: “why is it built this way?” But “why” is a terrible question for 2 reasons: It makes people defensive. Subconsciously, the engineers who built the system might feel threatened. They’ll start making up arguments to justify the system’s current shape. “Well, Redis on XXX…
saved by
related reading
- Everything I know about good system designseangoedecke.com
- Cognitive load is what mattersminds.md
- How To Do Lessalexturek.com
- Why Over-Engineering Happens | Yusuf Aytasyusufaytas.com
- What Actually Makes You Seniorterriblesoftware.org
- Do the simplest thing that could possibly workseangoedecke.com
- AI is removing the middle class of software engineeringblog.florianherrengt.com
- AddyOsmani.com - 21 Lessons From 14 Years at Googleaddyosmani.com
- The Elements of UI Engineering — overreactedoverreacted.io
- How to Write an Effective Software Design Documentrefactoringenglish.com
- Mistakes engineers make in large established codebasesseangoedecke.com
- Code-first vs. Product-firstthezbook.com