neverjust
neverjust.net · 540 words · saved by 2 readers
a guide to better developer communication
never just it's never just that simple Picture yourself wrestling with a complex problem - maybe it's an elusive bug in a legacy codebase, or a fragile system architecture held together by workarounds and technical debt. You've invested countless hours diving deep into the problem, meticulously mapping out dependencies and edge cases. Your mind is swimming with implementation details when someone casually drops in to say: Why don't you just... To the person offering, it feels insightful. They've cracked the code! They see the easy answer that has eluded you. But to you? It lands like a…
saved by
related reading
- Not Everyone Gets to Be a Beginner in Tech - DEV Communitydev.to
- Cognitive load is what mattersminds.md
- New Junior Developers Can’t Actually Code | N’s Blognmn.gl
- Don't ask to ask, just askdontasktoask.com
- How To Do Lessalexturek.com
- Nobody Gets Promoted for Simplicity – Terrible Softwareterriblesoftware.org
- Do the simplest thing that could possibly workseangoedecke.com
- Simplicity is An Advantage but Sadly Complexity Sells Bettereugeneyan.com
- How to Ask for Feedback - Sam Juliensamjulien.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com
- Why Over-Engineering Happens | Yusuf Aytasyusufaytas.com
- The Debugger's Toolkit - by Addy Osmani - Elevateaddyo.substack.com