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
- Stop trying to try and trymindingourway.com
- Impact, agency, and taste | benkuhn.netbenkuhn.net
- Trying to Try — LessWronglesswrong.com
- Stop trying to try and try — LessWronglesswrong.com
- Choose Boring Technologyboringtechnology.club
- Home - The XY Problemxyproblem.info
- #133: Dạo này mình ít hỏi Vì Sao - by Tuấn Monmanyonepercents.substack.com
- Losing the root for the tree — LessWronglesswrong.com
- Visa is doing marketing consults (see pinned!) on X: "in the 5+ years I worked for my ex-boss Dinesh, he constantly, casually-yet-intensely would ask me about my goals & desired outcomes "what do you want to get out of this?" "how willtwitter.com
- neverjustneverjust.net
- "What's my goal?" — LessWronglesswrong.com
- Focus on the places where you feel shocked everyone's dropping the ball — LessWronglesswrong.com