It should be testable. It should defend. It should be clear to understand. It should catch errors. If it is not the sole source of all the logging, it should provide valuable fragments that render what it logs usable. It should do what it is meant to do, not what we hope it to do
Yes, it does, there is bad code in the cloud, not all code, but a good amount. Because you can easily throw more “stuff” at it to make it more “elastic” and “spinning” up things makes it more performant. These tactics work in the short-term and get you out of a jam, but that’s all they are meant to be, if your code is performing badly, no amount of memory will ever make it run…
Every application has some level of Technical Debt. Some of it exists in our tracking systems, but most of it exists in our minds, slack channels, or forgotten conversations we have with each other, later to be forgotten when we start on something else. One of the hardest jobs of being a Software Manager is being able to enunciate where your team’s debt is and push the work that needs to be done, to get…
We all have leftover code lying around ready to be used. But like any type of leftovers, they are not perfect. They need to be reheated, perhaps rejigged into something else, maybe even dressed up a little more. No one eat’s leftovers as is, code snippet leftovers are the same, they are a start to something better.
If you’re looking for loopholes to save the day and get your project done or product out the door you better be prepared to keep looking. Because once you find one loophole, chances are you are going to need another. And once you find that one, you’ll then need another. Loopholes are cyclical implementations of constantly trying to find your way out of a problem of your own creation. The further down the loophole you…