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…
Good Leaders show up every day, keep things humming, and tell everyone they are doing a great job. Great leaders show up every day, they ensure the team is working on the right things at the right time and aren’t afraid to make a call to change the direction of the ship if it means the team can get better and stronger, they are always looking towards what is coming down the pipe, prepping it…
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…
You have a day full of meetings with 15 to 30-minute breaks in between. What can you accomplish that you can finish within that timeframe without returning an hour later and having to start all over again? It might take a while to figure it out, but that’s the idea, to think about it and have it ready when those moments do popup so that at the end of the day you aren’t wondering what…