Where companies struggle in their adoption of Agile is that they implement it within a small area of the company where they learn to do it really well. They get good at it and they get into a rhythm of what they are doing. They have tweaked the idea of Agile to meet their needs and goals and they have a system that is working and moving products and code out the door. What they…
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…
Try – What we are attempting to do. Catch – If what I was trying to do doesn’t work and it blows up, Wonder – Perhaps I should try this alternate path instead. It sounds nicer than Finally.
Every question has two responses. The knee-jerk, shoot from the hip, get off my back, I’m tired of this, you don’t know what you’re talking about, this is a waste of my time response. Or, the “take a step back”, read it again, don’t rush to respond, gather the information and this must mean something to you response. The latter doesn’t mean you are ignoring the potentially valid issue being raised, it simply means you…