A Lover of Delphic Wisdom
If there is a bedrock, bottom line, everyone-should-follow-it-all-the-time rule in programming it is “The DRY Principle” – Don’t Repeat Yourself. This simple rule states that you should write code once and only once, and that you shouldn’t allow the same code to be used all over the place. Or, as the Wikipedia article deftly states:…
If there is a bedrock, bottom line, everyone-should-follow-it-all-the-time rule in programming it is “The DRY Principle” – Don’t Repeat Yourself. This simple rule states that you should write code once and only once, and that you shouldn’t allow the same code to be used all over the place. Or, as the Wikipedia article deftly states:…
This page was orginally published on Wed, 05/05/2010 – 10:29 on my Embarcadero blog. The next principle for the “Pretty Good Practices” we’ll discuss is this notion: Whenever possible and as much as possible, put functionality in a class – preferably a class that can be easily unit tested, reused, and separated from any user…
Okay, hopefully by now you’ve read the introduction of this series, and you’ve downloaded (or better yet, pulled from source control) the latest version of TextScrubber and given it a once over. In this installment, I’m going to discuss the file structure of the project and why I did things the way I did. First,…
This post was originally made on Fri, 04/23/2010 – 14:35 on my Embarcadero blog. Okay, so for this first installment, I’ll be illustrating one of my core principles for developing applications: All my code of any importance at all goes under source control. All of it.I’m all by myself – why should I use…
This article was originally published on Mon, 04/19/2010 – 16:38 on my Embarcadero blog. A while back someone (I can’t remember who, sadly, sorry to the person who made the suggestion…) suggested that someone do a series of articles about “the best practices on how to develop a Delphi application”. That’s a good idea. There…