Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

81–90 of 101 posts

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

#81

Post by 8bitsrule »

If your code 1) runs the first time with no non-trivial errors or obvious bugs, 2) does at least what you intended it to do, reliably, efficiently, and isn't easily de-railed...

then you're getting close. If 3) you find you can easily and quickly modify it to add features... months later... that's closer still.

Of course if you have to answer to someone about why you did it this way or that way, or who can't comprehend your code, then (in that environment) you may have farther to go.

Longer, bigger, harder projects may test your skills. Be your own best critic, always strive to do more with less.

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

#82

Post by methusala8 »

jointpdf wrote: post #67

I wouldn't describe myself as a programmer, but I have spent a considerable amount of time and energy thinking about how to become 'better' as a data scientist (as well as how to encourage others to grow their skills and knowledge, and how to measure that growth). So, I can share some tips about learning in general (i.e. metalearning--"learning how to learn") that should apply no matter your field. If you devote your…

Can you add anything specific to Data Scientists in particular? I am in this field and would like to improve further. Any pointers would be helpful. BTW, Nice post. +1

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

#85

Post by xfitm3 »

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…

The problem with measuring effective is that it is quite subjective. Politics can skew those results.

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

#86

Post by pjc50 »

xfitm3 wrote: post #85
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…

The problem with measuring effective is that it is quite subjective. Politics can skew those results.

That's a skill like any other. If you're conspicuously bad at politics it can make you ineffective - you or your work will be sidelined or abandoned.

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

#87

Post by pjc50 »

zumu wrote: post #76
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…

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?

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

#88

Post by octosphere »

Some basic heuristics I use for determining the capability of other programmers and myself:

1.) Does the code have a good bus factor i.e If the maintainer dies tomorrow by being knocked down by a bus, can other people pick up where he/she left off? Further research into the Bus Factor can be found here: https://www.youtube.com/watch?v=0SARbwvhupQ

2.) Is the code well documented? This is so obvious that it is painful to write this comment, but it is a very simple heuristic for determining capability. Documentation can include code comments.

3.) Is the code resilient to weird input? The code should perform well under heavy fuzzing and where possible, sanitize different input. It should be tested against this: https://github.com/minimaxir/big-list-of-naughty-strings

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

#90

Post by cakes »

snackbugs wrote: post #43
Hbthegreat wrote: post #39

Earlier quoted context omitted.

This is the correct answer

No, it just means your boss likes you.

Disagree, I was the not in the "in crowd" with my boss at a previous location and yet I was the person (as suggested) in regards to everything backend related.
Post reply on HN