Morning friend ☕️

This week's post starts in my dad's workshop in the 80s and ends with the AI editorial engine I am building now.

Same instinct, forty years apart.

When was the last time you built something just to see if it would work?

What would you try if trying suddenly got cheap?

Grab your coffee.

Let's chat!

Before I was an engineer, a manager, or whatever hybrid creature I'm slowly becoming now, I was a kid trying to build toys we didn't have.

I grew up in the 80s, around TV shows and movies like The A-Team, MacGyver, Delta Force, and Airwolf. Naturally, we wanted to play war games.

We could afford the little green plastic army men. But the jets, tanks, helicopters, and ships? Not so much.

So I built them.

My dad was an artisan, so the raw material was everywhere. Offcuts. Sawdust. Blades. Nails. Glue. I had no training and no YouTube tutorials. Just curiosity, sharp woodworking tools I probably should not have been using, and a vague picture in my head of what a piece of wood was supposed to become.

The tanks looked like tanks if you were generous. The helicopters mostly required imagination. The ships floated mainly in theory.

Cricket was the same. It was massive in our neighbourhood, but when we were too young to have proper bats, we made them from planks and played with tennis balls until the plank split, the ball disappeared in the bush, or someone's mother called us inside.

You imagine something, you try to build it, it fails in some weird way, you adjust, you try again.

And somewhere in that loop you learn the most important lesson available to a child:

The world is not only something you consume. It is something you can shape.

That instinct eventually became engineering for me. A more formal version of the same impulse.

Instead of scrap wood, systems. Instead of toy tanks, software products, teams, deadlines, and production issues that always arrived at the worst possible moment.

But underneath, the same pattern remained: take something that does not exist yet, try to make it exist, learn from what breaks.

Many adults slowly lose access to that way of thinking.

At some point we stop asking "What can I build?" and start asking safer questions.

What am I qualified to do?
What will people think?
What if it fails?

And without noticing, we move from builder to spectator.

I've had to fight that in myself. Not by staying childish — childishness avoids responsibility. By protecting wonder, which keeps possibility alive.

Wonder is probably why I kept trying business ideas that failed.

The one I remember most clearly: if you've ever driven past a Builders Warehouse in South Africa, you've seen the men waiting outside with their hand-written boards: Tiler, Painter, Plumber. Skilled, but unemployed. Hoping to get picked for a few days of work.

We built an app to connect them with homeowners who needed help with DIY projects.

And here's the part that still stings: the technology worked. The app worked, the backend worked, the matching worked.

What failed was everything around the software: vetting, operations, persistence.

Mine included.

At the time it felt like wasted effort. Now I think of it as tuition.

Every failed attempt taught me something about customers, distribution, my own weaknesses, and how much harder execution is than imagination.

That's all a growth mindset really is: treating failure as data instead of a verdict. It matters because new things are always messy before they are useful, and the builder only survives by staying curious instead of becoming defensive.

Which brings me to why I'm writing this now.

For most of history, building something meaningful required access to resources. Capital, technical teams, distribution, knowledge. That access was unevenly distributed. It still is.

But AI is collapsing the cost of trying. Here's a small, unglamorous example from my own work.

Until recently, all the knowledge behind Scary Management — story canon, doctrine, the rules of the world — lived in a clunky Google Drive.

Every time I edited the book, I manually checked my changes against those documents. Does this scene contradict something from an earlier episode? Does this line break a rule I set for a character months ago?

Tedious, error-prone work that ate entire evenings.

Now an agent does it. Every edit is tested against canon and doctrine, and anything suspicious gets flagged for me to judge.

Not magic. Plumbing.

But it's the kind of plumbing that used to require a small technical team, and I built it myself, around a day job and a full life.

That's the shift.

The old question was: "Who will let me build this?"

The new question is: "What am I willing to learn how to build?"

I think this matters most for people like us.

Mid-career professionals with experience, scars, taste, and hard-earned pattern recognition. People who have survived enough restructures and strategy resets to know exactly what's broken. And who have ideas, but not always the time, team, or confidence to act on them.

AI does not remove the need for courage. But it reduces the cost of trying.

And that is why I believe the future belongs to the builders.

Scary Management is my own builder experiment.

I'm still finishing the book. I'm still learning how to use AI without losing my voice, judgment, or standards. But behind the scenes, I've built something that feels important: an AI-assisted editorial engine. Not a magic button. Not a content farm. A small team that helps me think, write, challenge, edit, and organise this universe while life carries on around it.

But the next series isn't really about my engine. It's about something older than any of my tools: the itch to make things before anyone gives you permission to. Somewhere along the way, building got expensive, and a lot of us quietly filed our best ideas under someday.

What I've come to believe is that building just got cheap again

So over the next five posts, I'll take you inside the thinking, not the technicals. No prompts, no agent-speak. Just the why. I'll use Scary Management as my example, but every post ends at your bench. Your project, your idea, your raw material.

Yes, I'm an engineer by training. You don't need to be. But, even though inspiration is wonderful, if you want to build something that survives real life, you eventually need a system.

And building one is far more human, and far more within reach, than the AI hype makes it sound.

The door is open.

Until next week, friend.
Vaugan