Ask HN: As a programmer, how do you know if you're a good one or not?

Post by zumu » Tue, Nov 27, 2018, 7:11 PM UTC

pjc50 wrote: post #87

zumu wrote: post #76

Earlier quoted context omitted.

Aside from the first question (may first 2 questions), the top questions are arguably more qualitative than quantitative. > Do I solve more problems than I create? Who judges what constitutes a problem? How do you know when you've created a problem? > Do I see simple solutions to complex problems? Define 'simple'. > Can I refactor terrible code to more easily maintained code? Define 'terrible'. How does one know what…

> Aside from the first question (may first 2 questions), the top questions are arguably more qualitative than quantitative. What's wrong with that?

Post by todd3834 » Tue, Nov 27, 2018, 8:17 PM UTC

redleggedfrog wrote: post #36

todd3834 wrote: post #26

My favorite definition of a “good” programmer is someone who ships! Done is better than perfect. Knowing what compromises to make in order to ship without creating a future nightmare.

Oh my gosh, no. That might be a "good" software developer, but I'd probably think not on that, too. I've had to follow behind such programmers who wrote their code with the primary goal of getting done as fast as possible never expecting to have to come back to it. It's literally the worst code that exists. Usually they no longer work at the same place they created such code, because later they were asked to maintain…

Post by HereBeBeasties » Tue, Nov 27, 2018, 10:26 PM UTC

Post by bb88 » Wed, Nov 28, 2018, 1:23 AM UTC

hdkmraf wrote: post #75

bb88 wrote: post #31

You're asking the wrong question. You should be asking "Am I an efficient or effective programmer?" Do I get things in on time / under budget? Do I avoid common programming pitfalls? Do I solve more problems than I create? Do I see simple solutions to complex problems? Can I refactor terrible code to more easily maintained code? Can I avoid terribly written code in the first place? Can I effectively communicate with…

Wow, this is such an eye opener. I have always considered myself an ok programmer, but always struggling with trying to be effective. Your four points on effectiveness happen to me on a daily basis, but I tend to see them as annoyances, mind you, I rarely refuse to help and advice. This gives a whole new light and meaning to all those interruptions.

Post by neptunius » Wed, Nov 28, 2018, 8:38 AM UTC

camel_gopher wrote: post #92

bb88 wrote: post #31

You're asking the wrong question. You should be asking "Am I an efficient or effective programmer?" Do I get things in on time / under budget? Do I avoid common programming pitfalls? Do I solve more problems than I create? Do I see simple solutions to complex problems? Can I refactor terrible code to more easily maintained code? Can I avoid terribly written code in the first place? Can I effectively communicate with…

One of my gotos has been 'Can I avoid writing code in the first place?' Zero code has zero bugs, and zero maintenance cost.