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…
When multi-core computers hit the mark, developers could now scale their applications to use most of each and every CPU at their disposal. To ignore them and run only one core was an utter waste of your application. The change to implement was worth it, the learning and the time were well spent because leveraging more of what the platform had to offer made a better story for all involved. The same with the cloud,…
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…
This is a question to ask your team – What kind of team are we? Are we the kind of team that follows the rules? Do we listen to each other? Do we tell each other what to do or coach each other? Do we push the envelope? Do we lead by example? It could be all of this, none of this, some of it, or more, but the important part is to know what…