A couple days ago, I introduced this series of posts. The first true post will be next Monday. However, before I begin I wanted to share two books that are very influential to me.
If you haven’t read these books, I highly recommend them. Not only do they make up the foundation of much of what I will be writing about, but also they are very informative reads with some good ideas. Neither should take too long to get through, particularly Rework, which is split into very short (think 1-2 pages) for each section. While Rework is primarily focused on a team or company level, there is plenty for an individual developer (or leader) to glean from it as well. As for The Clean Coder, well, that should be issued to every new developer that is hired by your company, assuming they don’t have a copy of it already.
If you have read one (or both) of these books, then you’ll recognize where my ideas are coming from. Granted, not everything I will be writing about is based upon points I found interesting in these books. A lot of it will be from my personal experience, and some more of those ideas found in the books were things I came to independently before reading them.
Of course, not everything recommended by these books will apply to every situation. In fact, you might completely disagree with them on some things. I can’t say there were too many things I found that were completely off the wall, although there may be things I don’t quite see as applicable or in quite the same manner as the authors.
Nevertheless, these books are well worth the time to check them out.
Latest posts by Andrew (see all)
- On Developers and Von Moltke’s Leadership Matrix - November 9, 2015
- Andrew’s Coding Corner- Beware the Sunk Cost Fallacy - November 3, 2015
- Andrew’s Coding Corner – Unit Test, Young Man, and Grow Up With the Code - October 27, 2015