After my oh-so-recent review of Best Kept Secrets of Peer Code Review, I followed up with the author to inform him of the review. I also took the opportunity to tell him that I disagree with him on a few points, not the least of which is the concept that finding a larger number of defects is good. His reply was gracious, and I hope to have an opportunity to further discuss some of these points with him. Meanwhile, I was inspired to carry on my rant here on the home front.
Archive
Author ArchiveI 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.
An 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. continue reading…
There are a few benefits to being “between assignments” (a.k.a. unemployed). One of them is that I can once again find time to post.
What is it about creating firmware that can make a seasoned journeyman software developer forget everything he or she ever learned about software design? continue reading…
Article, article, article, absense, absense, absense… So what’s the deal!? continue reading…
Some software architects tend to think a lot about our place in the software world. In a recent conversation with a colleague, I found myself in agreement with his description of the clear separation between software engineer and software architect. His argument wasn’t that the two roles couldn’t be fulfilled by the same person, simply that they are separate disciplines. I fully agreed, yet as I thought about it, I grew somewhat uncomfortable with my own conviction about the extent of this separation. I felt a need to try to establish what the relationship is, and perhaps what it should be. continue reading…
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.
While I have not worked directly with FAAConsultants, I have had several conversations with Todd, including a demonstration of their software product; and I believe that many firms who produce hardware or software that must comply with FAA regulations would benefit by its use. continue reading…
Most organizations today, and I would venture that all organizations involved in the production of high-integrity code use one or more development standards, in an attempt to improve the quality of the software produced. Among the common types of standards for development are Architecture Standards, Design Standards, and Coding Standards. Verification standards also exist, for the same reason. In this article, I will focus on coding standards, as that is where I have seen the bulk of issues. continue reading…
subscribe