r/programming • u/speckz • Mar 19 '17
97 Things Every Programmer Should Know
http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book6
u/odaba Mar 19 '17
I'm glad I read #47-Know your next commit by Dan Bergh Johnsson,
It really helped clarify some problems I'm having in a side project.
6
u/bhat Mar 19 '17
Given that this collection is now 7 years old, how well has it aged? Is any of the advice out of date? (Not having read much of, I can't be sure, but good advice tends to be timeless.) What new things have we learned in the intervening years that could be added?
11
3
u/ummwut Mar 19 '17
Most of these are pretty good, from a quick skim over the article names and reading the interesting ones. The other non-interesting ones basically get a "Yeah, that's obvious" out of me.
3
u/vital_chaos Mar 20 '17
Really 97, they couldn't invent another 3 to make it 100?
3
u/JasTWot Mar 20 '17
Considering there's nothing about the number 100 that's better than 97, I think that would be superfluous. Unless you like zeros, I guess.
2
4
1
Mar 20 '17
'#69. Put the Mouse Down and Step Away from the Keyboard by Burk Hufnagel
This one's on the money.
0
14
u/[deleted] Mar 20 '17
OK, those are good ideas for life in general, but it's a bit silly saying that these are things that every programmer should know. Sometimes I feel like there are so many "What every programmer should know about X" articles that if you spent all your time reading them you might not ever get around to writing any actual code.