Code is meant to be broken, reiterated over, broken again and again and again until it cannot function anymore. That is what code is meant to do. It works, it changes, it breaks, it gets fixed, it works again. Welcome to coding! Let the everlasting Frustration and Joy begin.
I was watching a lot of clips from Apollo 13 for a bit and one thing that kept striking me – their focus. I look at my desktop and sometimes see all the tabs of random thoughts occurring as I look at issues and problems and I think – “there is no way I could be in space, I’d have all these tabs and binders open just trying to figure out what to do.” Probably…
I was troubleshooting an issue today, trying to figure out why an automated build wasn’t working. It turns out I had to toggle a configuration value and then from there remove some steps. I found the answer on a random StackOverflow post where someone had a similar issue. This after 2 hours of trying different scenarios and pulling (what’s left) of my hair out trying to get there. The Hidden Configurations and back-end combinations of…
I spent the last few weeks trying to create a straightforward no-code app – login page, show a profile – I ended up going back to code to get it done in a few days. If I didn’t know the code, I would have had two options in front of me; Invest myself in a company’s specific framework and learn “their way” to do No Code. Not do what I want, but use some of…
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…