Why I Needed to Build Something Slowly Again
January 30, 2026
The first video was about what this channel is. This one is about why. Lately, life and work have been fine — no crisis, no reset — but I realized I’d been running on autopilot. Days were passing, routines were repeating, and I wasn’t really building anything on purpose. I was just moving. Software is where I notice this the most. When you’re deep in features and bug fixes, it’s easy to optimize for speed and stop asking the better questions: are the specs right, how do real people use this, and what happens when things break? Slow Builds is me stepping out of that mode. Not to be careful — to be honest. To pay attention again. And to document the process while I’m still inside it. This isn’t a launch video. It’s not a reset. It’s a record of showing up — even when progress is small and motivation isn’t consistent. If you’re building something quietly and trying to stay present while doing it, you’ll probably relate.
Read transcript
00:01 — Opening
Hey — welcome to Slow Builds.
(pause)
So the first video on the channel was about what this channel is going to be about.
(pause)
This one is going to be the why.
(pause)
And yeah… that last video was my first YouTube video ever.
It was pretty rough.
(pause)
My wife was pretty clear on how rough it was.
(small smile, pause)
For this one I still have a script — but I’m using it more as a guide.
I’m gonna look away. I’ll glance at it.
So there might be some pauses while I re-zone and find my place.
(pause)
That’s just me doing this… as me.
So I can get through it without being too nervous.
(pause)
And listen — I’ve still gotta figure out the lighting,
I’ve gotta figure out the mic,
and I’ve gotta figure out how to get a good flow.
(pause)
But that’s kind of the purpose of this channel.
Building slow. Learning as you go.
(pause)
So yeah — this video is more about why I’m building this… not what it is.
(pause)
⸻
01:20 — Autopilot
To bring it back…
a little while ago, life and work were moving great.
(pause)
Nothing was bad.
No stress.
It was almost like everything was just… autopilot.
Very automatic.
(pause)
Hours would pass.
Days would pass.
Weeks would blow by and you don’t really notice.
(pause)
I keep thinking about that movie Click — the Adam Sandler one —
where he fast forwards through life.
(pause)
Next thing you know, his kids are grown…
his whole life changed…
because he kept skipping the “small stuff.”
And that’s the stuff that matters.
(pause)
And recently, for Christmas, we went on vacation —
and it broke the routine.
(pause)
The workouts.
Waking up early.
Going to the gym.
Going to work.
Doing extra work at night.
Making supper.
All those things.
(pause)
Because everything was on autopilot.
(pause)
But that vacation made me realize something:
I was just moving.
Going through the motions.
(pause)
Not really building anything.
Not really growing.
Just living life and trying to get through it.
(pause)
And honestly… we all are.
(pause)
⸻
02:33 — I’ve always built things
And the thing is… I’ve been building things my whole life.
(pause)
Systems at work.
Systems in my own life.
Just helping out where I can.
(pause)
Building the algorithm.
Habits to stay on track.
(pause)
Some habits are great.
Some aren’t.
And you try to break those.
(pause)
And then apps — big ones, small ones — working with teams.
(pause)
So this wasn’t about not knowing how to build stuff.
(pause)
It was realizing I’d stopped being intentional…
about what I was building.
(pause)
I was just doing it.
(pause)
⸻
03:10 — Software is the clearest example
And I’m going to refer to software a lot on this channel,
because it’s what I do for a living.
(pause)
So it’s easy for me to see things… and explain things.
(pause)
It’s the biggest part of my life.
(pause)
And in code… when you’re deep in it —
shipping features, fixing bugs —
you start optimizing for speed.
(pause)
How fast can you get it out?
How many can you get out?
(pause)
Not like a competition…
but it starts feeling like a race.
(pause)
You know the code so well you don’t even have to think.
You just… push it out.
(pause)
And I really started to notice this when I had to review one of my coworker’s code.
(pause)
Everything worked.
It met the specs.
It had all the requirements.
It did exactly what it was supposed to do.
(pause)
But nobody was slowing down to ask:
(glance)
Are the specs right?
Is this how users really use the system?
What happens when something breaks…
or someone clicks a different button?
(pause)
And that’s when I realized… I do the same thing sometimes.
(pause)
Actually — most of the time.
(pause)
You fix the bug — it works.
You ship the feature — it passes the specs.
(pause)
But then it comes back… because it broke.
(pause)
And it’s like… you’re not making things better.
You’re making them work.
(pause)
You’re putting out what people expect…
but you’re not trying to make it the best it can be,
or cover all the bases.
(pause)
You’re not taking the time to really look at it.
(pause)
⸻
04:51 — What slowing down actually does
Slowing down gives you perspective.
(pause)
It lets you stop assuming…
that this is what everyone does…
or this is how it needs to be fixed.
(pause)
You can actually digest what’s happening.
(pause)
You slow down.
You take your time.
You look at it.
You think about it.
(pause)
And you can reassess.
Like…
“I think a user would do this…”
but what happens if the system goes down… and then that breaks?
(pause)
What should the user see?
What should happen in that case?
(pause)
What’s the best way for someone to click around…
jump around…
find what they need?
(pause)
What makes their life easier…
and in the end makes the software better?
(pause)
And yeah… sometimes I lose my spot.
(reset, small laugh)
So give me a second.
(glance, pause)
Okay.
(pause)
So yeah — it helps you reassess.
(pause)
And by doing all that…
you build a better product.
You build better systems.
(pause)
And if you apply the same mindset to your life…
it’s a better life.
(pause)
⸻
05:50 — What this video is (and isn’t)
So this is not a launch video.
(pause)
This is not a reset from video one.
(pause)
This is Slow Builds… getting into it… figuring it out.
(pause)
And this is really just explaining why I’m doing this.
Not what the channel is about —
but why I feel like I need to do this.
(pause)
Because slowing down forces me to pay attention.
(pause)
To name what I’m working on.
Name what I’m doing.
And why I’m doing it.
(pause)
If nothing else… this becomes a record of showing up —
even when progress is small…
and motivation isn’t consistent.
(pause)
It never is.
(pause)
You work out every day and you don’t see results.
(pause)
You write code all day and you keep hitting bugs.
(pause)
It always happens.
Nobody’s ever satisfied.
(pause)
You’re always gonna hit walls.
But it’s about pushing through… and keeping going.
(pause)
⸻
06:40 — Close
This isn’t about outcomes.
(pause)
This is about continuing.
Always showing up.
(pause)
I didn’t need to build something big.
(pause)
I need to build something honest.
(pause)
So this channel is me trying to do that.
(pause)
I’m gonna show my progress with the things I’m working on,
talk about different stuff as I go…
(pause)
…and this is where we start from here.