I just finished reading the “Best Kept Secrets of Peer Code Review (Modern Approach. Practical Advice.)“, by Jason Cohen. While this book is available from resellers at Amazon.com, for the time being it is being offered free of charge from Smart Bear Software, a software tool company founded by the book’s author. Continue reading “Best Kept Secrets of Peer Code Review – A Book Review” »
Archive
Tag: Tools of the TradeAn article was brought to my attention recently. It contains an interview with Bjarne Stroustrop, of C++ fame, discussing the language to which he gave life. Aside from a few technical non sequiturs, such as referring to C++ as “the archetypal ‘high level’ computer language (that is, one that preserves the features of natural, human language)”, I found the article rather entertaining.
In 1968, Edsger Dijkstra published the paper that put him on the map permanently in the minds of most of the software development community. While he made a number of very important contributions to computer science during his lifetime; I believe that “Go To Statement Considered Harmful” has spawned what has become perhaps the most enduring and pervasive religion in the annals of computing history. In my two-plus decades in the industry, I’ve seen only one coding standard which did not entirely prohibit the presence of the goto statement; and even that one that allowed it in one limited circumstance.
I wanted to express my thanks to Todd, over at FAAConsultants.com. He placed this site on his resource page, and we’re beginning to see some referred traffic as a result.
Continue reading “FAAConsultants.com: Compliance Made Simpler” »
When I originally titled this article, I had no idea just how appropriate it would turn out to be. Thanks to a series of events that has occurred over the past few weeks, this article has become a 3-time, self-referential do-over. Self-fulfilling prophecy, or simply an application of Murphy’s law?
Okay, that’s a bit strong, but it got your attention. In truth, I think design patterns are very useful things. They can aid in understanding software design, for documenting and communicating design, and for applying to or refactoring designs; but many people see them as something more. I saw a consulting job requirement a while ago, and one of the required skills was that the candidate “must have used ALL of the design patterns” documented in the GoF Book
