A New Blog

We are entering an age of computational acceleration. Those who are able to understand and use AI tools will become increasingly effective.

This blog will be a journal of the projects I build whilst exploring the latest advances in AI tooling.

A Build Log of sorts.

Why Busy Building?

I was sitting here thinking about how to name this blog when I tried to interact with a CLI tool I was using; it threw back an error at me

"Busy Building".

And that seemed rather fitting. My intent with learning these AI tools is so that I can become a more effective software engineer. So that I can spend more of my time building products and software, and less time doing everything else.

I am a builder at heart, and I want to spend my time doing that.

Why Create This Blog

I spend my working hours, and often much more than that, working on software for BigTechCo. I love my job, and think that the products we are working on are valuable to our customers. I have the opportunity to work with intelligent people, focused on solving problems at scale.

But in the last few years, I have stopped working on software for myself. In university, and early in the career, I was always busy building something for myself. That passion for building personal projects took a sideline position as my career became my focus.

In part that’s because the problems I was able to solve at BigTechCo were much larger in scope and scale, that I deemed them more valuable to work on.

But now with the continued improvement of underlying LLMs, and the tools built on top of them — a single developer in their spare time is able to be incredibly productive, and create real value.

This blog will journal my process of kick starting that passion for buildling once again, and share my learnings along the way.

Who Should Read This

My intention is to write content for myself, to help add clarity to my own understanding. That being said, if you are like me then perhaps you will derive some benefit from reading these posts.

My goal is to make exceptional software engineers at least 25%+ more effective. If through AI tooling we are able to make ourselves 25% more effective; a reasonable benchmark. How will that compound over a year? Over 5 years? Over an entire career?

That’s the question I want to try and answer with these posts.

As always, get busy building.