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

Re:Ask HN: As a programmer, how do you know if you're a good... by zumu on Tuesday November 27, 2018 @01:57AM (#18540123)

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 code is more easily maintained?

> Can I avoid terribly written code in the first place?

See above.

> Can I effectively communicate with people in order to get the answers I need without wasting their time with needless questions?

What constitutes "effective" communication? What are "needless" questions?

I generally agree with the questions, but I would imagine most programmers could read them and think, "I must be pretty effective."

[ Parent | on HN ]

Re:Ask HN: As a programmer, how do you know if you're a good... by pjc50 on Tuesday November 27, 2018 @10:18AM (#18542906)

> Aside from the first question (may first 2 questions), the top questions are arguably more qualitative than quantitative.

What's wrong with that?

[ Parent | on HN ]

Re:Ask HN: As a programmer, how do you know if you're a good... by zumu on Tuesday November 27, 2018 @02:11PM (#18545606)

OP specifically asked for quantitative metrics.

> So, as a programmer, how do you quantify or estimate how good you are?

[ Parent | on HN ]

Re:Ask HN: As a programmer, how do you know if you're a good... by bb88 on Tuesday November 27, 2018 @08:17PM (#18548454)

And I said he was asking the wrong question.

[ Parent | on HN ]