It’s Dangerous to go alone

We all love a simple story. A quick prompt in ChatGPT, grab the code and then back to what we were doing. However, building out a modern application is still more than a single sentence prompt in your LLM of choice.

Today’s applications are composed of an absurd amount of moving parts.

And you still have to build it.

If you choose to deploy outside of a PaaS, then you need to sit down and figure out your networking story. How are you going to manage DNS, network security, email configuration, delayed jobs, and more. Maybe you chose Kubernetes and now you are trying to wrap your head around all of these new nouns like: Pod, NodePort, and PersistentVolume.

My goal is to cut through all of the noise and help your team establish a common framework. Building on top of your previous decisions we will establish a common framework that will let your team work with confidence.

Be Curious

Over the years, one of my mantra’s, as a self-taught developer, is that “there is no magic in software.” In the end, everything in a program happens for a reason. It might be burried in 17 layers of gunk, but in the end it’s right there staring at you.

These something rewarding about grabbing your “keyboard and a flashlight” and dive head first into the mess. Find you way through the muck and find the solution. Doesn’t matter if its an accounting system, a software system, or a business process.

Now after two decades of doing this, you get to benefit from years of me asking “Why?” and generally being persistent until I understand. These software and human systems make sense to me, and are a continual curiosity for me, always leading me into new areas.

Something that feels unique to me after these years, is that I see software development as a means to study business. Much like Conway’s law states, I enjoy seeing how the departments and processes of a company impact and/or impacted by the software systems.