-1. Try to eat less, and choose healthy food choices.
-2. Get a little sunlight.
-3. Spend time around living creatures.<p>I spent the last few days inside putting together a website,
and I feel like crap. My normal aches, and pains are turning into something serious in my hypochondriacal mind.
Here's a cache of it if it's still down:
<a href="http://web.archive.org/web/20130914013327/http://programmer.97things.oreilly.com/wiki/index.php/Contributions_Appearing_in_the_Book" rel="nofollow">http://web.archive.org/web/20130914013327/http://programmer....</a>
Avoid embarrassing yourself, and our profession, by behaving like a hamster in a cage spinning the wheel.<p><a href="http://programmer.97things.oreilly.com/wiki/index.php/Hard_Work_Does_not_Pay_Off" rel="nofollow">http://programmer.97things.oreilly.com/wiki/index.php/Hard_W...</a>
Not sure I like #17 (<a href="http://programmer.97things.oreilly.com/wiki/index.php/Comment_Only_What_the_Code_Cannot_Say" rel="nofollow">http://programmer.97things.oreilly.com/wiki/index.php/Commen...</a> ). While I would prefer working this way, my colleagues probably won't. Reading code you haven't written yourself is tough and time consuming. If the code is accompanied by the 'natural language explanation' of the code, you get into the code quicker. The downside to this is making sure they stay up2date, which was probably why the author wrote the section.
This book is intended for beginning developers.
Tips like "put everything under version control" or "resist the temptation of the singleton pattern" or "floating point number are not real" are not exactly rocket surgery (pun intended).
(I own a copy, and consider it to merely be a shelve filler)
Here are the 97 contributions compiled in one gist : <a href="https://gist.github.com/pauletienney/6639605" rel="nofollow">https://gist.github.com/pauletienney/6639605</a><p>Pull request are welcome for text formatting, linking, etc ..