Never have been, never will be. We keep trying to solve them with technology, but they aren’t. The problem with meetings is that we all have different expectations of what they should and should not be, who should be invited, when they should begin, what their value is, and what should happen before and/or after them to make them a success and whether they should be on a recurring basis or not. But we don’t…
The smallest fix is the most critical release you will make to your software. It is the most critical because it is the most overlooked. “I ran it on my machine.” “It’s just this one isolated thing.” “It won’t affect anyone.” “We don’t have to tell anyone we’re deploying it.” Because it’s small we decide (for some odd reason) to treat it differently than our most significant releases and as such when something goes wrong,…
Yes. Or maybe it’s an area and not a room. We’ve been pretty flexible over the last few years where we met and got together and now we need to get back to doing that again when we are all together once more or when some of us are and some of us aren’t. The key to remember, which was always the problem before we went remote, was to ensure that everyone on board is…
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…
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…