Just ambling around the book store earlier I saw a 3 inch think tome around Go programming called Pro Go or something. I opened it and it was a whole book of instructional copy and paste recipes that span 10 pages for a simple problem. Urgh. This is the status quo now and it has been for a long time. I walked out with a book on pure mathematics instead - probably more useful in the long run...
Most programming books suck.
Yet he has some recommendations: But I do have this call to arms: my top five programming books every working programmer should own – and read.
They are: Code Complete 2 [1]
Don't Make Me Think [2]
Peopleware [3]
Pragmatic Programmer [4]
Facts and Fallacies [5]
1 - https://www.amazon.com/exec/obidos/ASIN/0735619670/codihorr-...2 - http://www.amazon.com/exec/obidos/ASIN/0321965515/codihorr-2...
3 - http://www.amazon.com/exec/obidos/ASIN/0932633439/codihorr-2...
4 - http://www.amazon.com/exec/obidos/ASIN/020161622X/codihorr-2...
5 - http://www.amazon.com/exec/obidos/ASIN/0321117425/codihorr-2...
I'm sure that's not the only case. Between the risk of drowning, and the difficulty for a lifeguard to tell between someone holding their breath underwater vs actually drowning, I'm not surprised a lot of pools have "don't hold your breath underwater" signs.
A more common drill we would do in practice were called "hypoxic" sets, where we would do one length of the pool breathing every 3 strokes, then the next every 5 strokes, then 7, 9 etc.. until you were going across the whole length (25 meters) without breathing. Not everyone could do it towards the longer distances without breathing, and the coaches would look out for "cheaters", but never once did anyone pass out. Maybe most swimmers, by way of the typical training and exertion in the pool, just don't develop a very good suppression of the "breath signal". I also never remember seeing anyone purposely hyperventilate so that they can stay under water longer.