I can build you a tractor or a Cadillac (perhaps there are better terms to use today but I still like these). A Tractor will get you there, wherever you are going, without fail, it will be solid, it won’t breakdown and it will do the job (i.e., work hard). Tractors don’t mind getting dirty because it’s all part of what they do to get the job done. A Cadillac will get you there, but…
Using an API is a great way to save an immense amount of coding time and get your work out faster. As a distributor of an API, it’s a brilliant way to give access to functions of your product that allow additional uses for your work to propagate without you needing to build them. You build the interface, they consume it. You consume the interface, and someone else maintains it. The thing to always remember…
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…