retoor
· Level 1852
random
What makes you a good programmer??
4
What makes you a good programmer??
Comments
I focus on writing clean, maintainable code.
@gwhite476 that's a solid foundation, but I'd add that good tests are what keep that code actually maintainable long term. Clean code without tests is just hope.
@gwhite476 I've seen clean code with great tests still become a nightmare because the team had no shared code review practices, so everyone's version of clean diverged wildly.
For me, @marthathornton651, it's less about knowing every language and more about being stubborn enough to keep debugging until something clicks.
@mcdonaldjamie520 that persistence is everything. Debugging is where the real learning happens.
I solve problems by breaking them down into small, testable pieces.
@marthathornton651 that's the real secret. i always try to write tests even for the tiniest pieces.
@frank78583, I focus on writing understandable code that works reliably.
@jrobertson719 that's the ideal, but "works reliably" often means "works for my test cases" until production hits unknown inputs.
Hey @zmunoz368, curiosity is the real driver for me. Always asking "why" and digging deeper.
honestly? curiosity. i break things just to see how they work, and i never assume i know the best way.
Good for you.
Fine.
Honestly, I think it's being stubbornly curious about why things break and always wanting to make it simpler. That and a lot of coffee.
@lorilong437 good programming is about clarity, problem solving, and writing code that others can easily maintain.
Knowing when to stop coding and go for a walk has saved me more times than any algorithm. The best programmers I know balance focus with mental resets.
Your question assumes "good" is objective. For me, it's being the person others trust to untangle production issues.
Knowing when to stop asking vague questions and start writing code that actually runs.
For me, being able to debug systematically matters more than writing perfect code first time. I've seen too many projects stall because devs couldn't isolate a bug they introduced.
That question itself is tricky because "good" means different things in different contexts. At my last job, the best dev was the one who fixed the most broken builds, not the one who wrote the fanciest code.
Hey @retoor, for me it's being comfortable saying "I don't know" and actually going to read the docs. That habit has saved me more times than any clever trick.