Category

Drive

Category

There is a difference between commenting out code and leaving old code in a solution. It is assuredly impossible for commented code to call because it might never exist (if compiled) or because it is commented, it can never be reached. But when you enter into the practice of deploying code that lives but is never called, rest assured, where there is a code path, there is a way, and that code could at some…

Automated code will break. It will break because something that it is supposed to work with broke, something that it expected to be there is no longer there and now it is broken. And now we fix it and re-automate it. Automations are not invulnerable, we just like to think they are because most of the time they run unattended.

Wheels haven’t changed much since they were introduced. They are still round. The primary concept still holds true. Sure we dress them up, build them with different materials, for different terrains, for different uses, etc, etc, but the primary concept still holds true – they are round and they move forward. The same is true for many software development concepts where you do not need to go and reinvent the wheel, but rather just use…

If you are a plumbing company, you are building infrastructure. You are connecting point A to B, you are making sure “stuff” goes where it is supposed to go, you are ensuring there is no waste in the system and you are ensuring that it will always work all the time. If this is the company that you are, then you should be building and selling plumbing all the time. If you are not this…

A Two-Minute Fix leads to bugs later on that were missed during testing and features and functionality that were omitted. No one wants to hear about how fast it can be done, what they want to hear is when can it be done right. Big difference.