5 ms·

Signs That You're a Good Programmer

44 points by theunamedguy 11y ago

greenyoda 11y ago
Interesting discussion from a previous post (about 3 years ago): https://news.ycombinator.com/item?id=5607823 https://news.ycombinator.com/item?id=5607823
dang 11y ago
A dupe of https://news.ycombinator.com/item?id=9167008 https://news.ycombinator.com/item?id=9167008.
- deleted 11y ago
  [deleted]
- theunamedguy 11y ago
  It's the opposite of a duplicate, actually.
  - dang 11y ago
    Sorry! Major Boolean fail. Un-de-duped.
draw_down 11y ago
I think probably these are signs of a good programmer. But i wouldn't worry too much about how you compare to these things. To be a good programmer, program.
deleted 11y ago
[deleted]
nqzero 11y ago
signs that you're good at writing clickbait on HN
kristopolous 11y ago
This list is kinda terrible. I know horrible engineers that can't get a single line in production code who match every one of these traits
fweespeech 11y ago
1) This is just HN clickbait. 2) The symptoms are largely hipster BS. ThinkGeek, Referal links to specific books, really? 3) A destructive pursuit of perfection is the sign of incompetence and is frequently career ending when combined with this symptom: "Contempt for delivery dates". The mere fact this was put to paper is proof the OP is completely worthless. If a developer can't produce an acceptable, working product on a reasonable deadline they get fired.
modarts 11y ago
A lot of these have a good amount of overlap with: "Signs That You're a Sociopath"
spo81rty 11y ago
Eager to fix what isn't broken should be more like getting better at your job over a period of time. Sitting around and rewriting apps that work perfectly to make cleaner/optimized code is not usually a good use of time. But taking lessons learned from one project to do better on the next is expected. No matter who writes an app, the next person in charge of it thinks it was written terribley and wants to rewrite it. This is a vicious circle and I have seen lots of development teams never achieve anything that really helps the business or users because of this. Be careful of ever being eager to fix what truly isn't broken.

44 points by theunamedguy 11y ago

Interesting discussion from a previous post (about 3 years ago): https://news.ycombinator.com/item?id=5607823 https://news.ycombinator.com/item?id=5607823

dang 11y ago

A dupe of https://news.ycombinator.com/item?id=9167008 https://news.ycombinator.com/item?id=9167008.

deleted 11y ago
[deleted]
theunamedguy 11y ago
It's the opposite of a duplicate, actually.
- dang 11y ago
  Sorry! Major Boolean fail. Un-de-duped.

draw_down 11y ago

I think probably these are signs of a good programmer. But i wouldn't worry too much about how you compare to these things. To be a good programmer, program.

deleted 11y ago

[deleted]

nqzero 11y ago

signs that you're good at writing clickbait on HN

kristopolous 11y ago

This list is kinda terrible. I know horrible engineers that can't get a single line in production code who match every one of these traits

fweespeech 11y ago

1) This is just HN clickbait. 2) The symptoms are largely hipster BS. ThinkGeek, Referal links to specific books, really? 3) A destructive pursuit of perfection is the sign of incompetence and is frequently career ending when combined with this symptom: "Contempt for delivery dates". The mere fact this was put to paper is proof the OP is completely worthless. If a developer can't produce an acceptable, working product on a reasonable deadline they get fired.

modarts 11y ago

A lot of these have a good amount of overlap with: "Signs That You're a Sociopath"

spo81rty 11y ago

Eager to fix what isn't broken should be more like getting better at your job over a period of time. Sitting around and rewriting apps that work perfectly to make cleaner/optimized code is not usually a good use of time. But taking lessons learned from one project to do better on the next is expected. No matter who writes an app, the next person in charge of it thinks it was written terribley and wants to rewrite it. This is a vicious circle and I have seen lots of development teams never achieve anything that really helps the business or users because of this. Be careful of ever being eager to fix what truly isn't broken.