We’re back to enforcing people to exist in person to trust that they will do the job. For two years we trusted everyone, we found the best and the brightest that got work done – we might have slowed down – but we got work done. And now we’re back to enforcing limits on how and where people can deliver from. What did we learn during this forced remote experiment that we all took part…
Guess what – MicroServices is no longer a big thing, Monoliths are back in the fold and soon n-tier will be the next big thing once again. While we are at, let’s think about what is the best for configuration files – registry settings, key vaults, database, json or .config files. There can only be one way that is right correct? I have a preferred architecture I like to go to every time I’m designing…
I can get into the coding zone. I can get into the coaching zone. I can get into the process delivery zone. But man, getting into that creative zone, especially when I’m tired, had a long day, and my mind is filled with questions – that takes work. Odd that it takes work to get into a zone where I can be creative and do something different. If your team is struggling to get into…
Here’s how you run performance, scalability, and load tests. Write down what you are going to test. Write down how you are going to test it. Write down how you are going to measure the test. Run the test. Report on the test. Rinse, Tweak, and Repeat Don’t worry if, in the first round, you get it wrong, that’s why you rinse, tweak and repeat to keep getting better and better at it. Most times…
Setbacks are minor disruptions in our plans to try something new. Blowbacks are the unintended consequences when someone comes down on us because our plan didn’t work. Setbacks are not equal to Blowbacks. We have the choice to recover from Setbacks, Blowbacks we have no control over (so stop worrying about them).