Editorial Notes: I originally wrote this post for the Infragistics blog. You can check out the original here, at their site. While you’re there, take a look around at the other posts by their contributing authors. If you were to take a poll of software development shops and ask whether or not they unit tested,…
Editorial Note: I originally wrote this post for the NDepend blog. You can check out the original here, at their site. If you like posts about static analysis, code quality, and the like, check out the rest of the blog. When I’m called in to do a strategic assessment of a codebase, it’s never the…
Editorial Note: I originally wrote this post for the SmartBear blog. You can check out the original here, at their site. While you’re there, have a look around and check out Collaborator, the code review tool. Let’s say that you wanted a definitive explanation, once and for all, as to what constitutes code quality. You…
My life has been undergoing some task thrash of late. That, combined with a decent amount of time doing car trips, has thrown me off of my recent reader question streak, in favor of cross posts. But, today I remedy that. A reader has a pretty straightforward question: “how do I write good code?” Here…
Three weeks, three reader questions. I daresay that I’m on a roll. This week’s question asks about what I’ll refer to as “how to de-brilliant your code.” It was a response to this post, in which I offered the idea of a distinction between maintainable code and common code. The lead-in premise was that of…
