Guides are documents that contain answers to questions you will encounter while you develop your applications. Some of those questions will be what should I use to prompt a user for input, and others suggest what is the best way to communicate your intent of the code you are writing Read more…
TODOs do not belong in the source code they get lost and forgotten. I was recently reminded of this when I had gone through some code to remove some code quality issues, that when resolved revealed that there was a to do in the comments of the code that had Read more…
A developer I work with had recently learned the lesson of what you see is not necessarily what you get. He had been troubleshooting some SQL to execute as part of automation script, and it kept failing. Everything looked correct, and it worked in SQL explorer but would give him Read more…
This weeks tip ties with the previous one: Drawing the Line, take one step at a time. Just like a bricklayer places one brick at a time to build a wall, you need to take on one code quality step at a time. Let’s continue with the previous example, you have Read more…
The chances are good that you have heard the phrase “Draw the line in the sand.” This line is the point you will not pass as to prevent worsening a situation. When dealing with code quality and craft, you will need to define that line, and the sooner, the better. Read more…
In the earlier days of computer programming, where punch cards were used to store our applications, there were a variety of ways to keep your code in order. One such method was to draw an arrow on the side of the card, and you would visually be able to see Read more…
For the past three months, I have been sharing code quality tips within my place of work in the hopes to help improve code deliverables. I am now moving the location of the repository to my blog in hopes that more than those at work may be able to increase Read more…