00:00 - Opening

Hey, welcome to Slow Builds.

Earlier I talked about how productivity systems often fall apart after a few months.

And it got me thinking about systems in general.

I think I finally understand why.

It has less to do with the system itself and more to do with human behavior.

And weirdly, the thing that made that click for me was our grocery list.

00:35 - The Analog System

For years we had a grocery list stuck to the fridge.

Just a piece of paper anyone could write on.

It was visible.
It was always in the same place.
It was simple.

And honestly, it did work.

Mostly it worked because I was the one getting most of the groceries.

At that point it was just me and my wife.

But now there are four of us.
Any one of us could go get groceries.
Any one of us could add something to the list.

And once that changed, the system did not work the same way anymore.

Like most systems, it worked... for a while.

01:20 - When The Friction Starts

Then the cracks started showing up.

Someone would already be at the store and someone else would go to add something to the list.
Now the list is not with the person at the store.

So you call or text.

Or someone realizes we are out of something right after you leave.

Same thing, another call or text.

Sometimes the paper just disappears.

Maybe it fell off the fridge.
Maybe it got moved.

None of this is a big deal.

But it is friction, and it starts to build.

02:05 - When The System Stops Working

The worst one is when you get to the store and realize the list is not with you.

Or someone calls because something was missed.

But the real worst one is when you come home and realize someone forgot to add something, or you missed something on the list.

And then you have to go back to the store.

After a while there is so much calling, checking, and missing things that people stop trusting the system.

At that point the system is not helping anyone.

You just go to the store and call home and ask what we need.

02:55 - The Usual Fix: Tools

When systems start failing, most people reach for better tools.

Better apps.
Smarter devices.
Automation.

You see this all the time at work, especially in tech.

There is always another tool you can buy or subscribe to.
Another platform that promises to fix everything.

I have been at too many companies where this happens.

Everyone convinces themselves this new tool will fix all the problems.

Sometimes the system quietly gets abandoned.

One or two people keep using it, but everyone else stops.

Updates stop happening.
Check-ins stop happening.

And the one person still using it starts sending emails asking people to update the system.

When the truth is everyone could have just said the same thing in the meeting.

04:00 - When Systems Become Forced

Sometimes it is worse than abandonment.

Sometimes people keep paying for the tool even though no one is using it.

And sometimes leadership forces everyone to keep using it.

Not because it works, but because they paid for it.

They invested time setting it up.

So now everyone has to follow the process whether it makes sense or not.

But tools only help if you actually understand the real problem first.

You have to understand the friction and the pain points before choosing the solution.

04:45 - What Was Actually Broken

Eventually I realized something about our grocery list.

The problem was not the list.

The list itself is actually the perfect solution.

Write items down.
Check them off.

You cannot really improve on that.

The problem was the process around it.

There were too many little rules.

Add things before someone leaves the house.
Make sure the list stays in the same place.
Remember to check it when you are at the store.

And the more people involved, the harder that becomes.

These systems only work if everyone follows the process.

The moment someone decides to go get groceries suddenly, the whole system breaks.

So the real problem was not paper.

It was access at the moment you needed it.

05:50 - Trying Digital

Once that clicked, the solution seemed obvious.

Make the list digital.
Share it.
Access it from anywhere.

But even that did not fully solve it.

And honestly, I was not about to start paying a subscription to solve a problem people have had since grocery stores existed.

So I started with the simplest options.

First I tried a shared Google document or spreadsheet.

Then we tried Apple Notes with a shared checklist.

But those still had friction.

People had to have their phones.
They had to open the note.
Type something in.
Clear items out afterward.

Sometimes people were not logged in.

Sometimes the list got messy.

It worked... but it still felt like work.

06:55 - The Unexpected Solution

Then one day the obvious solution appeared.

I was in the kitchen and used Alexa to announce dinner.

And it clicked.

We already had Alexa everywhere.

In the kitchen.
Living room.
Cars.
Phones.

We use it for announcements, lights, reminders, music, everything.

So I tried something simple.

"Alexa, add bananas to the shopping list."

And it worked.

Now anyone in the house can add items just by saying it out loud.

Kids downstairs can add something.
Someone cooking can add something.
Someone remembering something in the car can add something.

No phones.
No typing.

Just say it.

The system stayed the same.

But the friction disappeared.

08:05 - Reflection

I notice this pattern everywhere now.

Systems rarely fail in dramatic ways.

They fail in small, ordinary moments.

And most of the time it is not the idea that fails.

It is human behavior.

Nobody wants to add more work to their day.

When a system adds extra steps or forces people to change how they already do things, it slowly stops getting used.

New systems usually only succeed in two situations.

Either people need them badly enough that they are willing to completely change their behavior.

Or the system fits so naturally into what people already do that it barely feels like a change.

The Alexa solution worked because it did not change behavior.

It fit into behavior that already existed.

09:10 - Think Digital, Act Analog

Years ago I read a line in a book by Guy Kawasaki that stuck with me.

Think digital. Act analog.

The more systems I see fail, the more that line makes sense.

It is also why when I build something new, I start extremely simple.

Sometimes with paper.
Sometimes with spreadsheets.
Sometimes just a rough process.

Not because those tools are better.

But because they help reveal patterns.

You start seeing the real needs.
The real friction points.
Where systems actually break.

And once those things become clear, then it makes sense to build something better.

10:00 - Closing

So I am curious.

What systems do you use that actually remove friction and make life easier?

Let me know.

I am also planning to do a few videos about some small tools I am building for myself.

Most of them are simple things that help remove pain points in my own workflow and daily life.

And I am starting to think some of them might help other people too.

Thanks for watching.

Opening (00:00)

Hey, welcome to Slow Builds.

So I've been coding for a long time and most of my career has been spent deep in code, building, debugging, refactoring.

The flow state where you deep dive and disappear into a problem and when you finally resurface a few hours later, sometimes a few days later, you got something working and you're proud of.

And lately I've been more tired than usual.

Not burnt out.
Not overwhelmed.

I'm just very... I feel fatigued. I feel tired.

And if I'm being honest, AI is part of it.
And maybe even the cause of it actually.

I'm pretty sure.

Now I do feel that it's the major part and piece to why I'm feeling so fatigued all the time now.

---

When AI Feels Like Leverage (01:10)

At my job I work on a code base and I know it very well.

The parts that I interact with and build on I'm very familiar with.

And in that environment AI is very amazing.

If I let it build something inside a system I've lived in for years, I can review it quickly.

I know the patterns.
I know the edge cases.
I know what normal looks like in that code base.

And I can quickly see if something doesn't fit.

So at work and in that code base I can let it help me with things like:

• building documentation
• logging issues
• updating comments
• generating test cases
• creating new methods
• helpers
• small things

Sometimes big.

I can give it a full page and say refactor this or I need to add a new method that does this.

And I feel comfortable because I can quickly look at what it did, compare the differences, and I can point out if it went off the rails a little bit.

And to me that's full leverage.

That's taking a new tool and making my life better and more efficient.

---

When AI Changes the Role (02:40)

But when I'm building something new...

When I need to put a new integration into work code...

When I need to build a brand new tool inside of our system...

Or integrate something completely new...

Or the biggest part - personal projects.

When I'm starting from scratch it's a whole different ballgame.

AI is not just writing the code.

It's making decisions.

Sure, I give it an idea.
I give it some guidelines.
I open the door.

But I don't always know the mental map yet.

I don't always exactly know what the end result is going to be or what it should look like.

But by letting AI start working on it, it kind of assumes what the end is without me actually telling it.

So instead of just building, I'm reviewing a lot of assumptions.

I'm double checking a lot of edge cases.

Retesting everything over and over.

Comparing different approaches.

Comparing different branches of code just to see what differences there are.

Making sure nothing slips in.

No side effects.
No legacy code affected.
Everything backwards compatible.

So I'm less in a flow.

I'm more in supervision mode.

I've become a manager.

I'm not a coder.

---

The Verification Loop (04:15)

When I write something myself, I trust the reasoning behind it because I've walked through it in my head.

But with AI, even if it looks right, there's always this little nagging voice:

Did it miss something?

Did it break something?

So I review.

Then I test.

Then I'm rereading.

Then I'm comparing it to another approach.

So it becomes:

Generate -> doubt -> verify -> adjust -> verify again.

Rinse and repeat.

And that loop is tiring.

AI speeds up output.

Code comes quickly.

But pushing the code - deploying the code - comes slower because there's a lot of review in the middle.

And that review process is tiring.

Now I will say it makes the code better.

And it makes me better at spotting things.

But it's still a change in mindset.

And that change is where the fatigue is coming from.

---

The Constant Shifting (05:50)

There's another layer to this fatigue.

Every time I feel like I'm using AI right...

I feel like I finally have a workflow...

I read something online.

Or I talk to a colleague.

Or I watch a YouTube video.

And suddenly someone is using a completely different workflow.

A new tool drops.

A new model replaces something.

A better prompt strategy exists.

People are shipping systems faster.

Making money faster.

Getting traction faster.

And suddenly it makes you feel like everything you've been doing is wrong.

In my case I start considering scrapping everything.

Relearning everything.

Re-architecting everything.

Going deep into research mode.

Trying to figure out how to switch my process.

And this literally just happened to me this week.

I lost two days.

A lot of late nights.

And I scrapped a bunch of work.

All because another approach looked better.

And with AI right now it feels like the ground is constantly shifting.

It creates this constant low-level feeling of being left behind.

Even when I'm objectively getting more done.

---

Doing Something Is Better Than Nothing (08:10)

One motto I've always had in life is:

Doing something is better than doing nothing.

If you're not moving, you're dying.

Whether that's health.
Learning.
Or building.

And with AI sometimes the movement itself keeps changing direction.

But even if you're not doing it the best way...

You're still doing it.

You're still learning.

You're still building.

You're still part of this new shift.

And that matters.

---

The Energy Shift (09:20)

What's strange is...

More is getting done.

But I feel more drained doing it.

I used to get tired from building.

That was like a physical tired.

Like working out.

Now I'm tired from managing.

Reviewing.

Double checking.

Supervising.

It's a mental drain.

Sometimes it even feels like nothing got done.

Because I'm not the one writing the code.

It feels like there's this black box.

And I'm just poking holes into it to inspect things.

I'm less immersed in the code.

And much more in review mode.

And reviewing is exhausting.

---

The Pressure of Infinite Work (10:50)

I used to open my editor excited to knock out a bug or build a feature.

Now sometimes I hit a wall of tired before I even start.

And there's this background pressure:

"I should get back to it."

Even when I'm watching a basketball game.

Or going for a walk.

It feels like I should be working.

Because the work feels infinite.

There's always another refinement.

Another improvement.

Another optimization.

Another better way.

And it never ends.

---

Where I'm Landing (12:10)

I'm definitely not anti-AI.

If anything I'm a massive cheerleader for it.

I want to use it in every part of my life.

I use it every day.

Research.

Prototyping.

Organizing thoughts.

Summaries.

Analysis.

It genuinely helps me.

But I think I'm still rebuilding my energy system around it.

My role is changing.

From developer...

to something closer to a project manager.

And that's not what I trained to be.

---

Finding a Stable Path (13:20)

I don't need the most optimized workflow.

I need a stable one.

I don't need every new tool.

I don't need the flashy new way of doing everything.

I just need to pick a lane...

Stay with it...

And build confidence.

Because AI fatigue isn't about the tool.

It's about the role changing.

The environment changing.

The speed of everything changing.

---

Closing Thought (14:30)

So I'm still here.

Still adjusting.

Trying to take it one tool at a time.

Trying to stay involved in the code.

Trying to work with AI instead of just managing it.

And honestly...

I'm still figuring it out.

So if you're feeling AI fatigue too...

That might actually be a good sign.

It probably means you're in it.

You're learning it.

You're experimenting with it.

And that's better than running away from it.

Thanks for watching.

00:00 - Opening

Hey, welcome to Slow Builds.

The other night I spilled a full cup of black coffee all over a white-gray couch.
Completely black.
Total panic mode.

But somehow, that coffee spill ended with my wife and her parents telling me I need to get life insurance.

And the strange part is, when I actually looked into even trying to get it and did a couple quotes, the insurance companies themselves told me I probably should not be buying this because I do not seem to need it based on my situation.

00:30 - How It Escalated

So what happened is after the spill, and trying to do our best to clean it up, which I think we might have saved the couch, later that evening she went down to visit her parents.

Towards the end of that I started getting texts and phone calls just basically saying:

Go get life insurance.

Apparently the logic of how they got there was:

Oh, he spilled coffee. Maybe something is wrong.

What if it was a stroke?
What if he has a heart attack?
Do you have life insurance?
No?
Go get it now.
You need it.

So it was a very quick escalation from spilling some coffee to you might die.

01:05 - I'm Not Against Life Insurance

And now to be clear, I am not against life insurance.

Insurance just has to solve a real problem.
And that is the entire point of it.

You insure risks that would cause real financial damage if they happened.

So I started asking questions.

Why do we need it?
If I died, what would the money be used for?
What situation do you see needing to have the money?

And the only reply I kept getting was just:

Get it.
I do not care.
Get it now.

01:40 - So I Looked Into It

So when she did come back, she said pretty adamantly to go get it or she was going to go get a life insurance policy on me herself.

So I was like, fine.

Obviously it is probably not going to cost us that much.
And for a few dollars a month, I do not mind getting it.
Just for peace of mind.
To make her happy.

Because happiness and peace of mind is a lot.

If it costs me anywhere from like $8 to $20 a month, it is worth it.
Happy wife, happy life.

02:10 - What The Insurance Companies Said

So I did go online and I filled out questionnaires on a few different sites, and I was extremely honest about everything.

I did not hold back.
Debts, assets, income.
Extremely honest.

And two of the insurance companies actually came back and told me:

Based on your situation, we do not recommend getting life insurance.

Which you almost never hear from any insurance company.

Usually they are happy to sell you anything.
They will take your money.

And even the other one came back and offered a small plan.
It also said the same thing:

Based on your situation, we do not see a need for it.
But if you want a small plan to help cover funeral costs and unexpected expenses, this is what we would offer.

So I took screenshots of this and I sent it to my wife.

And I have not heard anything since.

03:00 - We Used To Have It

But the funny thing about it is, I do not know if she forgets or her parents forget, but we actually used to have life insurance.

A fairly large policy.

But it was back when it made sense.

We had more than one mortgage because we had rental properties and were just starting out in that game.
We had a brand new house that we lived in.
We had very young kids.
My wife was not working.

We had lots of debt.
Credit cards.
Lines of credit.
Mortgages.
New car debt too.

03:40 - Why It Made Sense Then

Also at the same time, because the kids were young, my wife was not working, and I was self-employed and flying out every Monday and flying home every Friday basically.

I was on the road consulting with companies.

So I could be in any city at any time during the week.
Bad weather.
Flying.
Getting to strange places.

This was before iPhone, so I had to print out my directions, get off a plane, and try to find my way.

I could end up in the wrong part of town.
It could be a snowstorm in a place that I am not familiar with.
I might get stuck somewhere.

You do not hear about planes too often, but God forbid, you never know.

So a lot of things could have gone wrong.

And my family was in a situation where if something did happen to me, she needed to have that insurance.

It made perfect sense to have a plan in case something went wrong that would remove the stress of having to worry about the finances, at least for a certain amount of time.

Because at that stage of our lives, with young kids, her not working, and all the debt, she would not have been able to survive on her own financially.

So that is when it made perfect sense.

04:50 - Life Changes

But life changes.

Time goes on.
The kids get older.
My kids are now in their 20s.
They basically take care of themselves.

Debt disappears.

Obviously there is always some small amount of debt here and there, but it is groceries, a trip you just went on, something you pay off.

It is not this massive debt sitting over your head that you are trying to chip away at.

We do not have that in our lives anymore.

Our savings are built up.
Our retirement funds are built up.

That is a big part of this entire channel.
Slow builds.
Investing.
Finances.

So over time, eventually what happens is you realize the thing that you were buying insurance to cover, you replaced it on your own.

You do not need the insurance anymore.

At this point, I would rather take the $20 or $50 a month it would cost me and buy some shares and build up my own personal investments and add to my dividend payouts.

To me, that makes more sense.

06:00 - The Question I Keep Coming Back To

So I keep coming back to the same question that I try to get her to answer:

If I died tomorrow, what problem would actually exist, and what do we need to cover it?

And in our situation:

She has a job.
We have investments.
She has her own.
I have mine.
We do not owe anything on our home.
It is maintenance mode.

We have a rental property.
We could sell it.
But it is also being rented at the moment, so there is income from that and it is an asset building on its own.

We do not have any major debt.

We did go on a vacation.
One of my kids has one semester left in school, so we help out with that.
But again, it is not something that is breaking the bank for us.

So we do not really have the same financial risk anymore.

If something did happen to me, she is taken care of by the things that we put away and by the things we did to get ourselves into this situation.

07:05 - What Insurance Is Actually For

And I think sometimes people misunderstand what insurance is actually meant to do.

It is supposed to protect against those big risks.

The things that, if something happened to one person in a relationship or family, would financially devastate everyone else and leave them in a bad place.

Possible bankruptcy.
Struggling.
Stress.

Sometimes people start insuring things they do not really need insurance on.

07:30 - The Car, Loan, and Mortgage Insurance Problem

The newest one, at least that I know of, is that when you buy a car now, you can insure the car payment itself.

Same with line of credit insurance.
Same with the mortgage insurance the bank offers you.

It is just an extra monthly payment so that if something happened to the person buying the car, the payments are paid off.

But the problem with those checkboxes is they only pay off what is remaining.

So if you get down to the last payment and you only owe $1,000, and something happens, well, you paid all that money month over month and they are only going to clear the debt.

So basically you paid all that money for $1,000.

Sure, there is some peace of mind along with paying every month.

But when you compare that to an actual life insurance policy, you pay the same amount every single month and if something did happen, you get the amount that you agreed to at the beginning of the term.

So if you had a car and you owed $25,000 on it, and you were paying the car company $10 a month for that insurance, then at the end of it, if there is no money left on the car, you just walk away with a car.
That is basically it.
You do not get any money.

Whereas if you only owed $1,000 on the car and something happened and you had a life insurance policy, you would get $25,000.

You put $1,000 on the car, you own the car, and you still have $24,000.

So there is a big difference between a lump sum policy and insurance attached to a product.

08:50 - How People Get Overinsured

And I think this is where a lot of people become overinsured, almost by accident.

Maybe they already have life insurance or some kind of policy somewhere, and that policy is already big enough to cover quite a bit of the expenses or things that might come up.

But then they go buy the car.
Or take out the loan.
Or get the mortgage.

And the checkbox is there.

Checking that box gives a feeling of relief.
A feeling of safety.

And that is why they do it right then in the moment.

Because they do not want to take the time to reevaluate their situation.

But in most cases, you probably are already covered, or maybe it is something you do not need to insure at all.

It is obviously not ideal to deal with trying to sell a car after someone passes away, but in most cases you could offload the car pretty quickly.

In the case of a property, property usually goes up in value, especially if it is something you live in or something that you take care of.

If you are the kind of person who is looking into life insurance, there is a good chance you take care of your home.

So there is a good chance that place is worth more now than when you began your mortgage or loan against it.

So having insurance that just pays off the line of credit probably is not the best case.

You are usually better off getting a larger lump sum policy if you actually need coverage at all.

10:10 - Reflection

Insurance is a very powerful tool, but it works best when it is solving a specific problem.

Otherwise it can quietly turn into something else.
Just another monthly payment.

And I think that is what made this whole situation interesting to me.

Because early in my life, life insurance solved a very real problem.

But when I sat down and looked at our situation today, I realized that problem does not exist anymore.

And that is something we do not talk about very often with money.

A lot of financial decisions are temporary, but they are also emotional.

A lot of times they make perfect sense in one stage of your life, and then quietly stop making sense.

Life changes.

And for me, life insurance was one of those decisions we did not need anymore.

Back then it solved the problem.
But today, after years of building assets and building stability, the problem it was covering is not there now.

11:15 - The Slow Builds Reflection

And I think that is something interesting about building slowly and the purpose of this channel.

If you keep paying attention to your finances over time, you start to notice that some of the protections you needed early on in your life eventually get replaced by the things you built.

Your savings.
Your investments.
Your assets.

And one day you realize something a little strange and exciting.

The thing insurance was meant to replace is the thing you already have.

You built it yourself.

And that might actually be one of the quiet milestones of financial independence.

Not when you can buy more protection, but when you realize you probably do not need it.

12:00 - Ending / Question

And I am curious about something.

Have you ever had a financial decision that made perfect sense early in your life, but later on you realized it did not really apply to you anymore?

How hard was it to cancel a policy or call up your bank to remove the mortgage insurance or line-of-credit insurance?

Was it a big decision?

Have you gone back and looked at those things to ask:

Has my life changed?
Is this something I could possibly go without?

Because that seems to happen more than people talk about.

And I am pretty sure there are a lot of overinsured people out there who are probably putting money in places that would be better used elsewhere.

Even if it is just going out for a date night, a movie, an extra coffee, or something small that improves life now.

That might be better than giving money to an insurance company for something you may not actually need.

Thanks for watching, and let me know what you think.
I look forward to the comments.

00:00 - Opening

Hey, welcome to Slow Builds.

So I've mentioned a few times now that I was going to explain how this channel actually started.

And the honest version is... AI built most of it.

I know that sounds very dramatic, but it's pretty much mostly true.

AI structured it.
AI outlined it.
AI named it.

AI pretty much did everything.

I'm just the one sitting here talking as awkwardly and as cringe as I am.

I'm just going along for the ride to see where this takes me.

00:39 - It Started With My Kid

This didn't begin with me wanting to be on YouTube.

My kid was posting on TikTok and started getting some really good traction - a lot of followers, a lot of views.

They wanted to move into YouTube for longer-form videos and just see what that would take.

So I did what I always do.

I started researching.

I wanted to figure out the YouTube algorithm, the best way to go about creating a channel, how to keep retention, what makes channels have longevity, and what makes a channel actually last longer - not just from hype.

And I kept coming back to the same thing.

You can't just throw up one video and hope it works.

Sure, you might get one video to go viral.

But you need consistency.
You need history.
Common themes.
A recognizable voice and image that people trust.

Once people start watching, they come back because they know what to expect.

And this is what I told my kid.

02:02 - The 52 Video Plan

At some point during this journey of researching for my child, I asked AI something simple.

If someone was serious about doing a channel - or even from my kid's point of view - how many videos would it take to build enough history that someone would actually subscribe?

Not just click subscribe and never see another video again.

AI suggested thinking in cycles.

Not viral attempts.

A full year.

One video per week.

52 videos.

That made it feel less emotional and more like a plan.

So I asked it to map out a year.

ChatGPT took the history of our conversations and everything I had asked it before... and it produced 52 video ideas.

It mapped out 52 titles.

It organized them into themes, pillars, and bridges between topics.

Then it took the first few and gave script ideas.

So suddenly there was a roadmap and a starting point.

And that's when it started to feel like this might actually be something real.

04:01 - Recording the First Video

Eventually I thought... let's just record one.

After redefining scripts and trying to figure out how I was going to keep track of everything, I just said:

Let's take the first one and record it.

AI helped with lighting, positioning, and the structure of the video.

I filmed it.

It was very awkward.

So instead of scrapping it, I dropped the entire video and transcript into AI and asked it to analyze it.

It came back with notes.

Adjust the script.
Change the framing.
Reposition things.

So I did it all again.

Not that it made much difference.

You can go look at the first video.

Even this video, I feel like I'm getting a bit more comfortable - but it's still hard.

Right now there's someone standing nearby and it's kind of freaking me out.

You might have heard the cat meow too.

I'm not in a setup that makes me feel fully comfortable.

But even with that first awkward video, AI said something interesting:

Just post it.
It's real. It's authentic.

Over time you'll get more comfortable.

05:45 - Locking In The Channel

At that point I figured if I was going to keep going, I should lock it in.

AI gave me several name ideas.

I went searching for domains and YouTube handles.

The idea was Slow Builds, but the best available option was Slow Builds Lab.

As a developer, that phrase meant something specific.

Slow builds usually means compiling code - waiting for your code to finish building.

But AI reframed it.

Slow builds as in time building things.

Compounding.

Growth.

Analytical thinking.

Once I had the name and the URL, it became real.

We had:

• 52 video ideas
• scripts for the first several videos
• a website URL
• a YouTube handle

At that point, it was happening.

07:12 - The Website (Built By AI)

The funny part is... yes, there is a website.

AI told me where to put it.

Since I'm already a developer and use GitHub all the time, I simply told AI to build me a site.

And it did.

The site is slowbuildslab.com.

It created an about page.

It generated a logo using Canva based on the name and early scripts.

The logo uses gears and growth imagery, which I actually like a lot.

AI also built the banner for the channel.

Getting the banner aligned correctly across devices was difficult because of all the different screen sizes.

But eventually AI figured it out.

08:33 - The Video Workflow

The workflow now is pretty simple.

AI helps generate:

• script drafts
• title ideas
• descriptions
• first comment
• thumbnail ideas

There's a lot of back-and-forth while shaping the scripts.

Once the script is ready, I film the video.

Like I'm doing right now.

I barely edit.

Usually I just trim the beginning and the end.

Sometimes adjust volume or reduce background noise.

That's about it.

After recording, I export the audio and run it through Whisper to generate a full transcript.

Then I add that transcript into my Apple Notes.

AI formats it into sections with timestamps.

Then I check if the title, description, or comments need adjustments.

Usually they don't.

Then the video gets uploaded.

10:49 - Updating the Website

Once the video is live, I grab the URL.

My Apple note contains:

• the title
• the description
• the pinned comment
• the YouTube link
• the full transcript

Then I open Codex and tell it a new video went live.

Codex reads the note, updates the website code, commits to GitHub, pushes the changes, and deploys.

Within minutes the video appears on the website in the correct order.

That whole system runs without me touching anything.

11:28 - The Hardest Part

Honestly, the hardest part of the whole process is the thumbnail.

AI image generation often changes my face too much.

So instead I grab still frames from the video.

Remove the background.

Give AI the thumbnail concept.

Tell it not to modify my face too much.

And that becomes the thumbnail.

It's pretty straightforward.

12:14 - Why I Wanted To Do This

One of the reasons I wanted to try this experiment is something I'm noticing on YouTube.

Some of the fastest growing channels right now are not hyper-produced.

They're raw.

Someone opens their phone and starts talking.

They might be outside by a lake.

Or sitting in a room like this.

The videos are messy.

Unedited.

Just humans being humans.

Long-form conversation.

With so much fast, short-form content everywhere, people seem to want connection again.

It feels like you're sitting there with the person as they think through something.

And that authenticity matters.

14:07 - Where AI Fits

AI removes a lot of the friction.

It helps write scripts.

Suggest titles.

Generate ideas.

Plan a full year of videos.

Without that help, starting from scratch would feel overwhelming.

Instead, I know there's always another idea waiting.

And as I keep making videos, new ideas get added to the list.

So the pressure disappears.

AI also helped with the structure, the thumbnails, and the website.

But when I hit record...

It's just me.

15:31 - Finding My Voice

The videos I like most lately are the ones where I go off script.

I start with the structure.

But then I just talk.

AI formats the sections afterward so I can stay organized while recording.

That helps me keep track of where I am without losing the flow.

Over time I'm getting a bit more comfortable with that.

16:16 - The Real Bet

The bet here isn't that AI will make this successful.

The bet is simply that I said I would try it.

Maybe it goes nowhere.

But I want to see if authenticity compounds.

If I can show up once a week.

Not perfect.

Not polished.

Just consistent.

And see whether people are interested.

17:03 - The Experiment

These videos aren't perfect.

They're not highly produced.

But I want to see if consistency keeps you in the game.

As AI becomes more common and more content gets generated automatically, I want to see if something simple still works:

A real person.

Talking honestly.

Showing up every week.

And seeing where it goes.

00:00 - Entering Something New

Hey, welcome to Slow Builds.

We're clearly entering something new with AI.

I don't fully know what to make of it yet.

There's a lot of excitement, a lot of noise - and there's also a lot of fear.

And to be honest, I'm feeling all of it.

I'm very unsure.

But at the same time, I'm very optimistic.

I'm excited to see what comes from this new age we're entering.

00:36 - Is This Another Industrial Revolution?

I've heard it compared to the Industrial Revolution.

And in some ways, that makes sense.

Back then, industries changed because we built factories and assembly lines. That infrastructure took decades. It was expensive. Change was slow.

If something needed to be modified, it wasn't easy. It took money, time, and effort.

This feels very different.

AI isn't replacing muscle first.

It's replacing thinking.

01:30 - The Middle-Class Question

AI is starting with cognitive tasks.

Call centers.
Paralegals.
Entry-level accounting.
Even higher-level accounting.
Junior developers.
Logistics planners.

Then you move into hybrid roles:

Truck drivers.
Taxi services.
Delivery systems.
Port operations.

Those physical-digital jobs could shift faster than we expect.

And that's mostly middle-class stability.

That's what worries me most.

Not collapse.

Compression.

Reshuffling.

02:33 - Ethics, Incentives & Power

The other thing that worries me is the people at the top.

Corporations building it.
Corporations deploying it.
Governments trying to regulate it.

Incentives move fast.

Sometimes faster than ethics.

Greed can move quickly.

And AI is powerful.

When something powerful moves fast, guardrails matter.

Empathy matters.

I hope the people steering this understand that.

Because we don't get unlimited resets with a tool like this.

Once it's embedded everywhere, it's hard to pull back.

We have to keep this one on the rails.

03:42 - The Question That Changed My Framing

The other day, I was out with a friend.

He asked me why I'm still building apps.

And I could tell what he meant.

At my age, I've built companies. I have a job I'm happy with. I'm not chasing anything.

He assumed I was trying to hit the big one.

The next Snapchat.
The next WhatsApp.
The billion-dollar exit.

But that's not it.

I just like building.

04:33 - Before AI: Friction Everywhere

Before AI, building meant friction.

You'd come up with an idea.

Then research it.
Document it.
Make stack decisions.
Figure out feasibility - technical, legal, practical.

You could burn weeks just validating an idea.

Now?

I can pick up my phone and start talking.

Type a thought.

Get an overview of what's possible almost immediately.

Build prototypes over a weekend.

Get architecture guidance.
Domain ideas.
Hosting plans.
Integration advice.
Even help shaping a sales pitch.

The overhead is dramatically lower.

05:50 - My Current Experiments

Right now, I have several ideas in motion:

A chores app.
A coaching concept.
A dividend tracker.
A trade tester.
A GPS tracker.
This channel.

Some are live.
Some are half-built.
Some might never launch.

And that's fine.

Because the goal isn't the unicorn.

It's creative output.

AI didn't make me more creative.

It removed drag.

06:54 - The WALL-E Fear

I joke about the WALL-E future.

Robots do everything.
We float around.
Unlimited entertainment.
No effort required.

Maybe some of that happens.

But I think something else happens too.

AI shrinks routine cognitive work.

And that expands creative leverage.

It's like having a small team behind you.

Engineers.
Researchers.
Documenters.

You still need taste.

Direction.

Judgment.

But you're not alone in execution anymore.

And that changes who gets to build.

08:22 - Different Perspectives, Same Leverage

One of my friends is a designer - a UX thinker.

He's not a coder.

AI lets him bring ideas to life without being blocked by code.

On my side, I understand the code deeply.

AI helps me move through it faster and focus more on user experience.

Different strengths.

Same leverage.

That's powerful.

09:11 - Holding Both Sides

So yes.

I'm unsure.

I worry about job displacement.

I worry about middle-class compression.

I worry about greed moving faster than laws and ethics.

But I also see:

Faster discovery.
Cheaper production.
Better medicine.
Smarter energy systems.
New businesses.
New roles we haven't even named yet.

Every major tool shift reshuffles value.

It doesn't delete it.

10:01 - Why I'm Leaning In

For people who want to think, build, and adapt -

This might be one of the most enabling ages in history.

That blows my mind.

I don't know where this era goes.

I don't know who gets hit first.

But I do know this:

I can build more now than I ever could before.

Not because I'm chasing something big.

But because the friction is lower.

That makes me want to create more.

10:39 - Closing

So yes.

I'm unsure.

But I'm optimistic.

My optimism outweighs my fear.

I'm glad I get to witness this shift.

We're living inside a chapter people will read about someday.

They'll say "before AI," the way we say "before the internet."

I'd rather lean into this and be part of it

than look away.

Thanks for watching Slow Builds.

I'd love to hear your thoughts on this one.

And yes - I let AI help shape this script based on my inputs.

That feels fitting.

Opening - "Why did I ignore it?"

Hey and welcome to Slow Builds.

I remember a friend telling me about Bitcoin in early 2012.

He started talking about how he watched a video introducing it. He had a friend who was mining it and told him about it.

Back then, the idea that we could "mine money" on our own computers made zero sense to me.

He was saying it was going to disrupt financial institutions.

And I completely ignored it.

And I'm a developer. I have a computer science degree. I have a math degree. I love investing. I love technology.

So why did I ignore it?

The dismissal - "It felt unserious"

For years I completely shunned Bitcoin.

I considered it hype. Vapor. Speculative noise.

Every cycle looked the same:

Up. Crash. Memes. Crypto bros.

It felt unserious.

There was no real backing to it.

The price swings felt random. They didn't seem to have any logical reason for why it would go up and then drop right back down.

And I told myself I was being rational.

I told myself I was being financially responsible by staying away from it.

I thought I was protecting myself from the nonsense around Bitcoin.

I thought I was protecting my money.

And I'm not saying I made the wrong choices.

I did make the right choices on some things.

Some things... no.

But Bitcoin is one I think I misjudged.

The turning point - a calm conversation

And what's funny is...

It didn't take one of my tech friends.

It didn't take a financial advisor.

It didn't take someone I look up to from an investment point of view.

It was one of my non-tech friends.

We were at a Hozier concert, out in a field.

He wasn't trying to pitch me on it. He didn't hype it up.

He just asked: "Did you see this about Bitcoin?"

And I basically said straight up:

"I don't buy into the hype. I don't invest in Bitcoin. I don't believe in it."

And he just started talking.

Not hype. Not "to the moon."

Just calm.

He talked about scarcity.

He talked about investment firms quietly buying it up.

He talked about governments experimenting with it.

He did the whole "futuristic gold" comparison - as an asset with limited supply.

He was measured.

And it stuck with me.

I walked away from that conversation thinking differently.

Going off-script: governments, debt, and narratives

I'm gonna go a bit off-script here.

This was around the time when Trump was coming into power again - I think it was that time.

And there was all this talk about debt, and government money, and bills that would allow treasury money to go into Bitcoin... and how that could offset debt.

A lot of it sounded like nonsense.

But it still opened my eyes.

Because it made me pay attention to something I hadn't really considered:

Governments are trying to use it.

They're trying to re-leverage debt.

And that kind of pressure could force Bitcoin into the "new asset" category.

Stores of value: gold, real estate, art, stocks... then Bitcoin

And that's where it comes down to this:

There are only so many stores of value in the world.

Gold is limited. It's hard to find.

You dig massive holes, go deep, just to find a tiny amount.

And even if you had gold...

In the future you don't want to be carrying coins and bricks around, chipping pieces off, weighing it like it's the old days.

Then you have real estate.

Land has always been valuable.

But land is expensive - and getting more expensive.

And it's not liquid.

You can't move a property "on a dime."

And owning property has overhead.

There's friction.

I've owned several rentals. I still have a rental, but it's family.

Still... there's headaches.

Floods. Mold. Vacancy. Collecting rent.

Property tax. Heat. Light. Water.

It's overhead.

Then you have art and collectibles.

Also limited. Also valuable.

But it takes a lot of money to buy in.

You can't buy "half" a collectible. You buy the whole thing.

And when you sell, you still need someone willing to pay for it.

Then you have stocks - tied to companies, revenue, growth, and what shareholders are willing to pay.

Outside of that...

You're kind of limited.

Shares.

Art.

Gold.

Material stuff - silver, bronze, diamonds...

Even diamonds are getting weird now because synthetic ones are flooding the market.

And then you have Bitcoin.

Digital scarcity - "21 million matters"

Bitcoin is a whole different kind of scarcity.

Digital scarcity.

There are only 21 million.

There's still about a million left to go, and that matters right now.

That's not like most cryptos where there isn't a real limit.

Where the supply can just keep expanding and the price can swing.

Bitcoin isn't like cash.

The US can print more money.

Canada can print more money.

You don't have that with Bitcoin.

It's not infinite.

And that's a structural constraint that forces value.

Once people agree it's worth something...

Because it's limited, each fraction becomes more valuable - as long as someone is willing to pay for it.

Theories: grounded, practical... and the wild AI one

So I have a few theories.

Including a pretty wild one.

The grounded one:

It becomes digital gold.

A reserve asset.

The practical one:

It's borderless value.

A way to transfer value between individuals and institutions without relying on banks, fees, currencies, cross-border friction, or regulatory overhead.

It's just... move value.

That alone makes it valuable in my mind.

Now personally?

I don't want to be the guy who buys pizza with Bitcoin.

I don't want to be the "40 Bitcoin Domino's pizza" story.

So for me it's set it and forget it.

Buy it slowly.

Take your time.

Slow Builds.

I bought some other stuff too - Ether, and a couple others.

But the majority of anything I put into crypto goes into Bitcoin.

Not most of my money.

But most of that crypto money goes into Bitcoin.

AI agents + money: what do they use?

And this is where my wild theory comes in.

It sounds crazy when you say it out loud...

But maybe there's something to it.

We've got OpenClaw.

We've got all these AI models.

You build agents.

Your agents go out, talk to each other, do work on your behalf.

And there are already stories of people giving agents access to bank accounts and credit cards...

And then they get wiped out.

Or the agent buys something insane.

Or signs up for some random course.

So if agents are going to go out and do things...

They're going to need to purchase things.

They can't just freely pass everything back and forth.

In my mind, they'll use some kind of digital currency.

And I think it's going to be Bitcoin.

Because AI agents could transfer it back and forth without relying on bank accounts.

Without currencies and fees.

Without all the limits and regulatory friction.

It's borderless. Frictionless.

A digital way to purchase and transfer value - agent to agent - to complete tasks.

We have no idea where this goes.

But it's a thought.

Bitcoin as the "measuring stick"

And even if Bitcoin isn't the one they use directly...

I still think Bitcoin becomes the underlying measuring stick.

Like gold used to be.

Gold to USD.

We don't do that now, but things start somewhere.

Bitcoin is finite.

Limited.

It's established.

It hasn't been "cracked."

It works.

So I think it becomes the default standard that everything else gets compared to.

When it drops: fear, opportunity, and narratives

Right now the price is dropping.

And I don't panic.

Maybe it's macro.

Maybe it's liquidity cycles.

Maybe it's big players moving markets.

Or maybe it's just human pattern-seeking.

I don't know.

But what I do know is...

It's a scarce asset.

And it doesn't feel "safe" when it's falling.

Bitcoin feels stupid to talk about with people who aren't tech.

People who can barely use an iPhone.

People who still use cash to buy a candy bar.

They'll never understand it.

But when I see the market drop...

I see opportunity.

Yes, it's still way higher than it was in 2012.

But it's also a better opportunity than it was six months ago... maybe a year ago.

Now I can get in at a better baseline.

Manipulation theory + "losing the middle"

And this is where I go off on my own theory again.

I have a feeling the Bitcoin market is being manipulated.

I think governments and financial institutions are still moving forward with their plan.

They didn't just drop massive amounts of money and walk away.

They put in orders.

They don't care what the price is in the moment.

They're buying.

And they already own a lot of Bitcoin.

And I think what happens next is...

They try to lower the price so they can buy more.

They scare retail investors.

People sell at the lows.

And the big players scoop it up.

Meanwhile, for poor people - it still feels too expensive.

Sure, they can buy tiny fractions... but most won't.

And don't listen to me - this is not advice - I'm just rambling.

But the point is:

They lower the price.

They buy more.

And people who panic lose their chance.

For me?

I see it and I want to buy a bit more.

So when it jumps back up, I'm not chasing it.

And this is how we lose the middle again.

More poor.

More rich.

Less middle.

That bothers me.

It ties into AI, money, everything.

We keep losing the middle.

Compounding, holding, and leverage (not selling)

I'm not rich.

I'm not in the rich category.

I'm just trying to keep my head above water.

But with Slow Builds - the way I buy things and hold things - I believe in compounding.

That's why I want to buy Bitcoin.

And I don't plan on selling it.

I'd rather leverage it later.

If the value goes up and I still own it...

I can use that asset as leverage.

Just like I leveraged my home for a line of credit.

You leverage assets.

You don't sell them.

Because once you sell them, they're gone.

If you own land, shares, art, collectibles, real estate, Bitcoin...

If you own it, you can leverage it.

So if one Bitcoin is worth $100,000...

I should be able to get a loan for $50,000.

Minimum.

And then maybe you use that money to buy other assets.

Again - my numbers might be off.

This is not advice.

I'm just thinking out loud.

Please don't go spend all your money because of anything I'm saying.

Closing - "I'm not laughing anymore"

So this isn't about going all in.

It's about recognizing something I dismissed.

Bitcoin used to be a joke in my head.

A meme coin at best.

But Slow Builds isn't about chasing hype.

It's about noticing structural shifts early enough to participate...

Without betting the house.

If Bitcoin is hype, it fades.

If it's digital scarcity, it compounds over decades.

I don't know which it will be.

But I'm not laughing at Bitcoin anymore.

That's the shift.

I buy it regularly.

I believe in it.

And even if it doesn't become what I think...

I'm no worse off.

At worst, it's still an asset worth something to somebody.

Maybe I lose some money.

Maybe I make some money.

Maybe it becomes something we all need later.

Or maybe it disappears.

But I'm in the game.

I'm in it for the long term.

And it's one of my slow builds.

Hey - thank you.

00:00 - This Is Not a Tutorial

Welcome to Slow Builds.

I want to start by saying I'm not an expert.
This is not a tutorial.
This isn't a "how to write better prompts" video.

I'm not here to teach you how to use AI properly.

I'm just trying to make sense of something I noticed.

I got my 2025 ChatGPT Year in Review.

And it said I'm in the top 3% of all ChatGPT users.

Also... top 3% of first-time users.

Both surprised me.

And honestly?
I didn't feel proud.

I felt uncomfortable.

Because most days I feel messy using it.

01:30 - Early Tech, That Part I Understand

The "early user" part makes sense to me.

I've always gravitated toward new tools.

Early Twitter.
UserVoice when it was brand new.
South by Southwest during the early SaaS explosion.

We were from the early wave of startups and internet tools growing up in small-town Canada.

So being in the first few percent of users?

I can grasp that.

But top 3% overall?

That scared me a bit.

Because I still feel like I have no idea what I'm doing.

03:00 - I Feel Like a Hot Mess

When I use ChatGPT:

• I rephrase constantly.
• I correct it.
• I correct myself.
• I restart mid-sentence.

Half my chats start with:

"This might be dumb, but..."

And end with:

"Wait. That's not what I meant."

So part of me wondered-

If I'm top 3% and still this unsure...

What does that mean for everyone else?

04:10 - So I Asked It

Instead of guessing, I asked ChatGPT directly:

"You put me in the top 3%. How?"

If you look at volume alone - new chats started -
I'm nowhere near the top.

I don't use it like Google.
I don't fire off quick one-off searches.

The difference, it said, was depth.

I go deep inside conversations.

I stay in them.

I follow up.
I push back.
I clarify.
I ask for alternatives.
I ask it to go deeper.

It values sustained dialogue over quick surface usage.

That made sense.

05:30 - How I Actually Use It

I don't delete chats.
I return to them.

Trips.
Car purchases.
Family texts.
Recipes.
Side projects.
Work integrations.

I'll stay inside one thread and keep building.

Even on walks with my wife.

We once spent an entire 30-minute walk troubleshooting why the pool chlorine kept dropping.

It became a third voice in the conversation.

We could interrupt it.
Correct it.
Ask for clarification.

It didn't replace thinking.

It extended it.

07:00 - Code, Quality, and Going Deeper

I use it heavily for code.

But not to blindly generate more.

I use it to:

• Refactor.
• Re-examine.
• Challenge assumptions.
• Ask if there's a better structure.

There's a narrative out there that AI makes developers ship bloated code.

Maybe.

But I think that's a usage issue.

The tool isn't the problem.

The intent is.

09:00 - It Wasn't Volume. It Was Staying in It.

Being top 3% didn't mean I mastered AI.

I don't have:

• A giant prompt library.
• An elite workflow.
• Fancy automation chains.

It was about staying in the conversation long enough to reach clarity.

Not accepting the first answer.
Rephrasing.
Refining.

That repetition taught me better prompting over time.

11:00 - Messy Is My Default

I use it the way I think.

Midstream.
Switching directions.
Throwing in random thoughts.

In one chat I might ask:

• Who's the shortest NBA player?
• How long to roast a chicken?
• Would an eSIM work for an app idea?

It's chaotic.

But it mirrors how my brain works.

I don't use it to move faster.

I use it to get unstuck.

There's a difference.

12:30 - The Awkward Phase

Most people quit during the awkward phase.

When answers feel generic.
When you don't know how to ask better questions yet.
When you feel like you're "doing it wrong."

I didn't get better because I mastered it.

I got better because I stayed awkward longer.

I kept opening it.
Kept asking.
Kept refining.

14:00 - Context Changes Everything

Over time I learned something simple:

If I need something serious,
I give it context.

I tell it who to be:

• Senior developer
• Therapist
• Investor
• Chef
• Life coach

Not because it's magic.

But because clarity creates better output.

The constraint improves the result.

15:30 - "It's a Time Waster"

I see people saying ChatGPT kills productivity.

And I understand how that can happen.

But that's true of any powerful tool.

Your phone is incredible.

Navigation. Banking. Work. Communication.

It's also three hours of scrolling.

The tool is what you make it.

If you use it to escape,
it becomes escape.

If you use it to build,
it becomes leverage.

Most days, I use it to build.

18:30 - You're Probably Not Behind

If your prompts feel messy...

If you constantly rephrase...

If you restart mid-chat...

You're not behind.

You're probably early.

As long as you're opening it,
trying,
experimenting-

you're ahead of the people who refuse to touch it.

20:00 - It Learns You Slowly

By staying in longer conversations,
it starts learning how you think.

My recap reflected:

• My work as a developer
• My family dynamics
• My travel preferences
• My personal goals

That didn't happen from one-off prompts.

It happened from continuity.

21:30 - A Slow Build on a Fast Tool

This isn't about mastering AI.

It's about staying in the conversation long enough
for it to compound.

It's a slow build
on top of a tool that's moving fast.

And that feels very on-brand for this channel.

00:00 - Opening

Welcome to Slow Builds.
So this one again is another rambling that I'm gonna go through.

And this one's more of an investment one.

And when you make investments, sometimes they don't work out the way you felt they should've...
or you got in at the wrong time.

But you always have to look at your investments - in my mind - as full-on long term.

And you just gotta go with the ups and downs.

So...

00:32 - Buying Nike at the worst time

I bought Nike pretty much at the worst time possible, in my mind.

I bought it right at the peak - not the peak, I guess - but one of the largest peaks they'd had for a long time.

It was well over $100 a share.

It was right before COVID.

They had just brought in a new CEO.

Things were looking great.

And then... yeah... COVID hit.

00:55 - Nike felt untouchable

The stock was doing great for a while because - like I said - anywhere you looked...

Every team, every sporting event, at the mall, every show...

No matter what you looked at or where you went, you saw a swoosh.

It seemed like everyone had it.

They sponsored everything.

Great stories were being told.

Great support.

Everything felt really good.

But then... like I said... COVID hit.

01:29 - COVID made the CEO's idea "work"

They had that new CEO who happened to come in on a high.

And he came from a background that didn't really fit that type of market... and that kind of product.

But because of COVID...
and the whole situation surrounding that...

his ideas worked.

Which... did it hit a lot?
Yeah.

01:55 - The biggest mistake: go direct, cut stores

His biggest mistake was he saw the sales going through the roof - shoes flying off the shelves - and he's thinking:

"Let's cut out the middleman."

"Let's go direct to customer."

"And let's get rid of the stores."

And you know what? Perfect timing - stores are shut down.

Nobody can go in and buy anything or try anything on.

So everyone's online buying.

It's the perfect situation for someone who doesn't really understand the product...

...but yet his idea manages to work.

02:29 - It worked... for that moment

And it did okay in that time frame because it gave customers a way to still get the product they wanted.

They were able to go run.

Like you couldn't buy a treadmill.

I live in Canada and my treadmill was broken and I couldn't get one.

So I'm running outside - and where we are it's pretty cold.

I'm talking... no wind... minus 20 Celsius.

Because I had to run... and I had to have my Nikes... because that's what I wear when I run.

Actually... I do wear Nike... but they stopped making the one I love... so now I'm a second runner.

But regardless.

03:13 - When COVID ends, people want stores again

So he managed that.

But then what happens is...

When COVID's over, people want to get out.

They want to go to the stores.

They want to talk to people.

They want to be in that environment.

And what happened in my mind is...

during that period, these stores still gotta put something on the shelves.

They still need product.

And if Nike doesn't want to be there...

other brands fill the hole.

03:57 - Shelf space shift: On + Hoka get their chance

And that gave an opportunity for the up-and-comers - the brand-new ones - like On and Hoka.

They got to fill space that normally they wouldn't even get a shot at.

New Balance has always been around - they got more shelf space.

Saucony - I've always worn it - it's always been there.

But again, they fill a void.

04:15 - Shoe retail background: reps + training mattered

And shoppers want to touch and feel.

And the other thing is...

I worked in shoe retail for quite some time - in my university and high school years.

Nike and Reebok - and all these brands - would send reps with the shoes.

They'd go store to store...
or set up nearby...

And they'd teach you about the products.

What the product's for.

What's new about it.

What changed.

Who it's not for.

And that makes a huge difference.

Because your salespeople are knowledgeable...

and they can help people make the right decisions.

And when you help someone make the right decision...

and that decision happens to be a Nike shoe...

they're gonna buy a Nike again.

05:14 - Runners are loyal

We used to get runners come in and they'd ask me about shoes I didn't even know were coming out yet.

And if it wasn't there... they'd just leave.

I didn't understand that at the time because I didn't run.

Now I get it.

I know exactly what size, which shoe, which make.

Unless there's a new model.

That's the only time I tinker.

06:00 - Customers try the new brands... and Nike loses share

So... shelf space gets taken over.

You've got On and Hoka and other brands filling that space.

The customer gets a chance to try them.

And sure - these are great shoes.

No issues.

And true runners are loyal.

Once they find something... they don't like to change.

Blisters. Ankle problems. Shin splints.

You gotta be careful when you run a lot of miles.

So Nike lost that market share right there.

And that's hard to get back.

06:59 - Second mistake: killing story + innovation

And on that front...

he took away the storyline.

He took away the athlete.

He took the heart and soul out of Nike, in my mind.

He tried to make it like a machine - just pumping stuff out.

You can't just knock out the same thing over and over again and hope people buy it just because it's iconic.

Dunks. Dunk lows. Skateboarding. Jordan.

You can't just regurgitate.

08:28 - Combined impact: off shelves, no story, no innovation -> stock drops

So all this together...

taking it off shelves...

losing market share...

taking away the story...

no innovation...

So what happens?

Stock goes down.

They're losing revenue.

Share price drops.

And again - I bought it at the worst time thinking Nike's everywhere.

09:31 - What I do: I double down (average down)

But again... what do I do?

I double down.

When I buy a stock and believe in it and I see the price drop...

to me that's a chance to average out.

I always believe it's gonna go back to where it is.

With Nike, I believe there's a new beginning.

10:42 - Nike reset: board + consumers spoke

Nike realized it.

The board realized it.

Shareholders spoke.

Consumers spoke.

People moved on.

But no matter how much the others grow...

their revenues combined still don't meet what Nike does.

And the one thing Nike has the ability to do - even when they look like they're suffering - is they can push back.

11:59 - New CEO brings back wholesale + innovation

With the new CEO back in - he was there before - I can't remember his name...

he brought back innovation.

He said: Nike is an innovation company.

This is what we do.

They brought back wholesale.

Foot Locker. Dick's. All those stores.

Now they're carrying it again.

Back on shelves where it needs to be.

12:42 - Nike can fund innovation others can't

And Nike is slowly gaining it back a little bit in running.

I always go to running because that's the biggest thing I do.

Hoka and On mainly do running and walking.

They don't have the budget to spend hundreds of millions... or a billion...

to chase the next evolution.

Whereas Nike can go try to make the fastest marathon shoe.

They can push track and field.

They can test crazy ideas.

Some might end up in the garbage.

But Nike can afford that.

15:35 - Stories are coming back too

And he's bringing back the stories.

He's bringing back what makes Nike, Nike.

That feeling...

when you wear it... and you believe.

And outside of running, they have so many other avenues.

I just don't see Nike failing.

Which is why... again... I double down.

17:15 - Slow builds / long-term framing

So I guess what I'm saying as part of this channel is...

I bought something knowing I was gonna hold it a long time.

I knew it was high.

But I thought it would at least stay there... maybe move up slowly.

I wasn't looking for a rocket ship stock.

This is something that chugs along.

Pays dividends.

18:46 - Dividend + DRIP + compounding

And here's the other thing...

they didn't drop their dividend.

They even increased it.

So even though the price is down...

I'm able to get a little more.

And the amount of money Nike makes is still massive compared to almost all of them.

So they're working from a place where they can learn.

And turn it around.

19:52 - Why I wanted to release this now

This is why I wanted to get this video out.

Because everywhere I look now they're talking about the innovations.

They're talking about the mistakes.

They're talking about reversing it.

And I'm like... man... I've been talking about this forever.

Even friends have said: "What price do I need to buy some now?"

And I'm like... I hope it does go back.

Because I've been buying at the low.

20:30 - Investing fear: "what if the market goes down?"

And I have a lot of people in my life who are scared of investing.

Their biggest thing is:

"What if the market goes down?"

"What if I lose all my money?"

And I always say... if you lose all your money...

those companies don't exist anymore.

And if banks, energy, telecom, pharma... all disappear...

we have way bigger problems than our portfolios.

21:36 - Price drops are a feature (for long-term dividends)

And then I always say:

Dividends reinvest.

Price drops are awesome.

Because the dividend buys more shares.

If the price goes up, I get less.

So over time... I actually want those downs.

So with Nike... I'm glad it's down.

It's a chance to get more cheaper.

22:09 - Closing

Again... this is the long game.

This is a slow build.

I'm taking my time.

I believe in Nike.

I've always loved Nike.

There are certain brands I stand behind.

And I really believe they're gonna turn this around and make it a great thing.

Alright. Thanks.

00:00 - Opening: This Is a Ramble

Hey, welcome to Slow Builds.

This one's a ramble.
Maybe even a bit of a rant.

It's the first time I've talked about investing on this channel, and that's part of my slow build philosophy. It's something I take seriously.

And this one comes from a little frustration.

Not anger.
Just... confusion.

00:40 - Why This Is Personal

This comes up because of my daughter's boyfriend.

He qualifies for a disability.
He wants to work.
He is working.

And I'm trying to convince her to make sure he follows through on this.

But there's hesitation.

And that surprises me.

Because she understands investing.
She's maxed her TFSA.
She contributes to RRSPs.
She talks about big goals.

So I don't understand why this one feels hard.

02:30 - What the RDSP Actually Is

In Canada, there's something called the Registered Disability Savings Plan.

If you qualify medically and you're working:

• You open the account.
• You contribute.
• The government contributes.

That's it.

The part I love most?

You have to work.

This isn't just free money for doing nothing.

You qualify, you participate, you contribute.

04:00 - The Simple Math

Let's break this down simply.

If he puts in $500 per year:

The government adds:

• $1,000 bond (while eligible)
• $1,500 grant (on the first $500)

So that $500 turns into $3,000 for the year.

That's not hype.
That's math.

$42 a month.

That's less than eating out once or twice.

And the government is effectively putting in about $208 a month beside it.

05:50 - Over Time (The Boring Part That Matters)

From age 20 to 49:

Out of pocket: about $15,000 total.

Total in the account (just deposits, no investing):
Around $80,000.

That means roughly $65,000 of that is government money.

That's what I mean when I say:

You're leaving money on the table.

08:45 - If It's Invested (Set and Forget)

If you just invest it conservatively.

Nothing crazy.
No chasing dreams.
No Tesla bets.
No gambling.

Just something boring. Broad. Dividend ETF. Even bonds.

Let it drip.

Let it compound.

Now you're not looking at $80,000.

You're potentially looking at $150,000 by 49.

Which could throw off $400-$500 a month in income.

Layer that with:

• CPP
• OAS
• Maybe GIS depending on situation

Now retirement doesn't look scary.

11:30 - The "You Can't Touch It Until 60" Problem

This is where the hesitation comes in.

You can't touch it until 60 without clawbacks.

But that's the whole point.

It's a retirement program.

It's designed to be untouchable so future-you is protected from present-you.

And honestly?

That's a feature.

Not a flaw.

13:00 - Why I Actually Agree With This Program

People with real disabilities often hit income ceilings.

Not because they're lazy.
Not because they don't try.

But certain roles require things not everyone can do long-term:

• Social intensity
• Leadership energy
• Executive functioning
• Stress tolerance

So earnings flatten.

The RDSP feels like the government acknowledging that.

Saying:

"If your lifetime earning potential is structurally lower, we'll help offset it."

That feels fair to me.

15:30 - The Other Side: Lifestyle Creep

Now compare that to people who can move up.

They make more money.

But what usually happens?

Bigger house.
Better car.
Lifestyle inflation.

They don't pay themselves first.

Then 40-50 hits.

And panic sets in.

Because salary went up...

But assets didn't.

18:30 - This Is the Part That Gets Me

It's $500 per year.

Not per month.

Per year.

And over 30 years, it removes pressure.

It removes panic.

It builds dignity.

It builds optionality.

And I just don't understand leaving that behind.

21:00 - Dream Big... But Build Slow

I don't want my daughter not to dream big.

I love that she dreams big.

"I'll be a millionaire by X."

Great.

But you still do the slow builds.

You still pay yourself first.

Because if the big dream works?

You won't regret having an extra $150k sitting there.

And if it doesn't?

You won't regret protecting yourself.

24:00 - The Real Frustration

Yes, people abuse systems.

Yes, that bothers me.

But this program has guardrails:

• You qualify medically.
• You open the account.
• You have to work.
• You wait.

It rewards participation.

It rewards effort.

It rewards time.

26:00 - Closing

You don't need to get rich.

You don't need to gamble.

You just need to not leave money sitting there.

If it's offered...
And you qualify...
And all it takes is $500 a year...

Take it.

Set it.

Forget it.

Let it compound.

That's it.

Hey, welcome to Slow Builds.

I think we've been taught that if something feels easy, it doesn't count.

And then if you use help, it just means you're cheating.

I don't think that's true anymore.

I cheat all the time.

Not on standards or quality, never on my wife, and definitely never on taxes.

Only on things that cause friction.

Things that slow me down, and almost always on the boring stuff.

Because nobody wants to do that. One place I cheat quite a bit, intentionally and unintentionally in a lot of ways, would be fitness and nutrition.

It's done in a way to keep me motivated, to not burn me out, not to make it feel like a burden all the time.

So one example would be like if you go to the gym, you're going to do your three sets of press and you want to hit 10 to 12 reps per set, but you hit eight and feel like, "I'm done."

You know what? You're there. That's the big win right there. The fact you showed up. You're there and you had a goal. You might not have hit it. That's fine.

Another one is the treadmill. I run on treadmill a lot, and I run outdoors a lot.

But I find that the treadmill and the Apple Watch don't line up all the time.

So it feels like there's kind of a cheat where I can run a little faster, go a little longer when I'm indoors on the treadmill if I only go off the watch.

And I'm fine with that.

Because then when I go outdoors, what happens is it is GPS. It is true. There's no lying on that one.

And when I see that my numbers outdoors are not hitting the same as the treadmill, I feel like, "What's wrong?"

Like, I'm faster than this, so I speed up and I do my best to hit those numbers.

So it's sort of like a little motivational cheat code in that sense.

And same with calorie counting. I've always counted my calories.

Calories in, calories out. That's it.

If you don't care about having a muscular body and you just want to lose weight, it's just about counting your calories.

Don't eat those bags of chips or that double scoop of ice cream. Eat a salad without extra dressing and extra cheese.

Have healthy options. Have your chicken breast with rice and some broccoli, and you're good to go.

Sauce is what kills you.

But anyway, what I mean is you track it, and I work out quite a bit, so I know what everything kind of is.

But I also know that not everything is tracked for what I burn.

If you take the stairs instead of taking the elevator, or use the bathroom downstairs so you take extra steps, or you shovel instead of letting the plow do all of it, that's all movement.

And I find what happens in that situation is I'm allowed to have that croissant or that Polar Bear ice cream.

Sure, on paper it looks like I didn't burn as many as I'm taking in, but there's a little bit of a cheat there and I reward myself with that.

I don't fret about it because I've been through it and I know it.

Another place that cheating really comes into play and makes life easier is special moments.

For gifts and stuff like that, especially Christmas, Valentine's, anniversaries, photo books.

We all have millions of photos. Everything is photographed and everything is backed up in the cloud.

Instead of wasting time trying to figure out the perfect gift that I think is perfect, I throw together a photo book.

Pick a year. If you went on a trip that year, usually that's what I do.

I'll take all the pictures from the trip and make a specific Bahamas book or New York trip book or anything like that that brings it all back and floods the memories.

In the end, people like those gifts the most. They're simple, but more meaningful.

And when we have so many pictures, I just print them all.

Another hack I do with that is I use Instagram.

When we do go on a trip, I post everything to Instagram, and that becomes my photo album that I can go off of, plus all the other ones.

We usually have boxes and envelopes full of pictures just sitting around.

Any other day, it gives us something to do to go look at those pictures.

Another one is handmade cards.

I know that feels cheap to the person making it, like school-grade handmade Valentine's or handmade Christmas cards.

But again, people love those the most.

And this is where AI fits into the picture and where we start moving into useful places we can use AI.

One example: two years ago, it was our 25th anniversary.

As kids, we called ourselves Pooh and Roo.

I gave AI a prompt. I said, "How would Roo ask Pooh, and what would Pooh say when asked how long 25 years is?"

Boom, it came out with the perfect response, like it came right out of Pooh's mouth.

Then I needed an image for this because it was too good.

I asked, "Can you draw an image of Roo and Pooh in the Hundred Acre Wood watching the sunset?"

Awesome.

Then you use Canva or Staples, throw it together, and in less than 24 hours you've got a printed card.

You made it yourself, you tweaked it, but you did use AI.

So it's a cheat, but it's the best kind of cheat in my mind, because those are the ones that stick around a long time.

Those are cherished a little more than going down to the grocery store or Hallmark and picking something someone else did.

Sure, AI wrote text for me, but it was my inspiration. It was our history. I picked what went there.

I was able to create it myself.

And that's the way I like it.

I've done examples before where I use AI on a daily basis, and it's sort of like a cheat too.

Before I send texts, if I feel emotional or reactive, emails, text, or even confronting someone, I'll put it in AI.

I'll give it context about the situation and say, "This is what came back, and this is what I'm thinking about responding with."

It helps me slow down and reframe it.

Most times it's spot-on, or it'll ask me: Do you want to be confrontive? Do you want to resolve this or make it worse? What is your end goal?

It helps me revisit what I would say and keeps me out of bad situations.

So it's cheating in a way. It gives me nudges in the right direction.

Another place is recipes.

I use AI for recipes all the time.

I don't like going to the grocery store and then realizing I don't have one expensive ingredient I only need once.

So I use AI for substitutions.

I have this, I want to make this, what goes together, what kind of sauce goes on it, what's good for quick dressings.

I even started tagging recipes in an ongoing ChatGPT project called Food.

It condenses them, puts them together, knows what we like, and gives me quick ideas.

Then I can ask, "I have this in the project, what can I make from the recipes we have?"

And like I mentioned before, and I'll do a deep dive video in the next few, this channel itself is heavily supported by AI.

AI helps with script ideas, ordering, thumbnails, descriptions, comments, and my website workflow.

I say that, but I've learned pure AI scripts don't work best for me because I feel like a robot.

So I get a script and ad-lib off it to make it more me.

AI handles the structure, which takes pressure off.

I don't edit these videos much, and I'm pretty bad at editing.

When we go deeper on cheating, one thing I notice is I "cheat" on one AI with another.

I'll use ChatGPT, then Grok, then Claude, depending on the task.

For recent events, I find Grok often has better current context.

I use ChatGPT for most day-to-day thinking and drafting.

I use Claude for larger code and document tasks that need deeper processing.

Sometimes I use ChatGPT to help generate prompts I then give to Claude.

That's another way I cheat.

As a developer, another cheat is repetitive code.

If I need to check whether an object has name, and whether it's nil, blank, empty, etc., I don't always want to rewrite that pattern.

I'll use Copilot or Codex to scaffold it fast.

That's not breaking standards. That's removing repetition.

Then I ask: should this become a reusable method?

Maybe it already exists in our system.

Claude helps me find similar methods across a large codebase, evaluate whether one can be extended, and avoid breaking other things.

That happens super fast.

Then we have a robust method everybody can use.

Sure, AI helped write it, but it was still my idea and judgment.

Same thing with tests.

AI writes test drafts for me.

I still run them, verify them, and make sure everything passes.

At work, I also use AI for Jira work.

We have Claude connected to Confluence, Jira, code, and Slack.

I can brain-dump messy notes and have it produce clearer tickets and docs that architects, designers, and PMs can review.

That helps me focus on actual implementation.

Right now I'm also testing a personal setup with OpenClaude and agents.

Agents for docs, tests, git, implementation updates, and status reporting.

They run multiple times a day on cron jobs and send Telegram or email updates: what's done, what's blocked, what needs review.

Then I focus on features.

I prompt for a feature idea, we prioritize it, break it into sprints, and agents pick up queued work.

I still approve code, review tests, and decide what ships.

But repetitive orchestration is automated.

That's the ultimate cheat, and I'm excited about it.

So I guess in the end, what I'm saying is: yes, I cheat.

And cheating is okay in this context.

As long as it's not illegal, not harming relationships, and not lowering standards.

I don't want AI to replace my thinking.

I still want authenticity.

I want it to be me.

I just want to outsource the busy work, remove repetition, and reduce friction.

I don't want lower quality in the work, the product, the meal, or the gift.

I want less unnecessary effort around the things that matter.

If something saves me time and helps me stay consistent while I focus on what actually matters, I'm okay with that.

To me that's not cheating. That's being smarter.

I'm not trying to win by cutting corners.

I'm trying to stay in the game long enough to compound.

Thanks for sticking around. Hopefully you enjoy this video.

Hey, welcome to Slow Builds.

Over the years, I have rebuilt my productivity system more times than I can count.
Every time, I am convinced this is the one.

It has that New Year's resolution feeling: new year, new you.
You are excited, motivated, and certain this time will be different.
It feels clean. It feels simple. It feels manageable.
You think, "I figured this out."

And for a while, it works.
Some things do stick.

I find the ones that stick usually have outside pressure:

• you are doing it with other people and do not want to be the one who drops it
• money is tied to it
• there are medical reasons with real consequences
• or there is a hard deadline and no choice

But most of the time, it fades.
Not all at once.
It fails slowly.

Until one day you realize you are just not doing it anymore.

I have fallen for this so many times.
I have failed at most systems I set up.
A few survived.
Some I only finished because the end of the year was close and I wanted to check one resolution box.

Over the years I have tried a lot:

• Getting Things Done by David Allen
• Basecamp
• Monday
• email labels
• notebooks and handwritten lists

I was not casually experimenting. I believed in these systems, and I still do.
They are built for a reason, and they can work.

But for me, most fail around month three.
There is no dramatic crash.
You just quietly abandon them.

There is always that moment at the beginning:
You rebuild everything.
You clean your tools.
You archive old tasks.
You create fresh boards and tags.
You feel empowered.

"This is clean."
"This is manageable."
"This is me now."

And for a week, maybe a few weeks, you are on top of everything.
You are consistent. You check it every day.

Then life shifts a little.
Nothing crazy.
Just enough.

Work gets busier.
More meetings.
Deadlines.
Family stuff comes up.
Long days add up.
You get tired.

You skip one day.
Then another.
Then opening the system feels like work.

Not because tasks are hard.
Because the system itself starts to feel heavy.

You dread opening it because odds are there is nothing you can check off anyway.
So why even look?

All you wanted to do was get simple things done:

• check the air in your tires
• clean the treadmill
• clean the shower

But now you have to "do the system" just to do the thing.

I convinced myself recently I had solved it with Apple Reminders and Apple Notes.
Simple. Clean. Convenient.

I organized tags, smart lists, timed reminders, linked notes.
It felt efficient.

Then one random task popped up and I froze.
Where does it go?
Does it need a new tag?
Does it need a schedule?

Then it became:
Do I need to update everything else too?

Fixing the system became the main task.
That is when it starts to fall apart.

What is interesting is there is rarely a dramatic quitting moment.
You usually do not delete the app.
You do not announce you are done.

You just stop opening it.

The longer you stay away, the harder it feels to return.
Backlog builds.
Missed check-ins.
Overdue tasks.

Then guilt shows up.
You try to use the system not because it helps, but because you feel you owe it.

At that point, it feels like the system is judging you.
Keeping score.
Adding pressure.

That is the part I missed for years:
Most productivity systems do not run on structure.
They run on motivation.

That "new setup" feeling is the fuel.
When it wears off, you see what the system is made of.

At first everything feels clean.
Then every task becomes another decision:

• what tag?
• what time?
• what list?
• does it need a note?

Now the system is not helping you do tasks.
It is asking you to be motivated enough to manage the system.

If it only works when you feel "on," it is not durable.
It is a good mood with a dashboard.

That is why month three matters to me:

• month one is novelty
• month two is momentum
• month three is the test

Does it still work when you are bored?
When life is messy?
When motivation drops?

The thing that keeps a system alive is design.

By design I mean:

• does it make starting easy?
• does it survive missed days?
• does it work when energy is low?

If not, it is not really a system.
It is motivation with extra steps.

What actually survives for me is simple:
Put things where I already know I will look.

There is no perfect system for everyone.
At work, tools like Jira, Basecamp, and Monday make sense.
They exist for projects, deadlines, and coordination.

For personal life, I keep rules simple.

Email:
If it is important and I cannot handle it now, I leave it unread.
I check email all the time, so unread means I will see it.
If days pass with no follow-up, it probably was not urgent.

Reminders:
I use reminders for personal tasks and review once or twice a week.
Not perfect, just predictable.

Calendar:
I am known for missing meetings if I rely on checking the calendar.
So I rely on notifications: one day before, four hours before, ten minutes before.
Email plus device notifications.

I am not trying to build a perfect system.
I am putting things in places I trust.

And this is the key shift:
The goal is not organization for its own sake.
The goal is relief.

When something stays in your head, it loops.
It interrupts you while driving, while relaxing, while trying to focus.
It creates low-grade stress.

My wife does this in her own way.
She writes notes on paper towels with a Sharpie and puts them where she knows she will look: fridge, door, mirror.
Strategic places, based on time.

It is simple, but it works.
Because it gets things out of your head.

Once your brain trusts that a task is parked somewhere reliable, it stops carrying it.
That frees space.

You focus better.
Think better.
Build better.
Create more.

That, to me, is the real win.
Not productivity points.
Not optimization theater.

This also connects to why I am building AI systems right now.
I want AI to carry repetitive, mentally heavy work in software development:

• documentation
• test creation and execution
• merge support
• deploy management

The idea is not to remove responsibility.
The idea is to automate standard busy-work so I can review output and spend more brainpower on product thinking, features, and real use cases.

It is the same principle:
Get mental load out of your head so your best thinking has room.

Another shift for me was pressure.
I used to love last-minute adrenaline.
University, work, side projects.
I would leave things late, sprint, and feel sharp when I pulled it off.

But that is not discipline.
That is adrenaline.
And it is not sustainable.

Then I over-corrected:
Finish early, but hold delivery so I would not get more work.

That also failed.
Because those "free days" were not free.
The unfinished thing still lived in my head.

Now my rule is simple:
Finish it, clear it, then rest for real.

So back to the main point:
If your productivity system fails, it does not always mean you failed.

Maybe it was not discipline.
Maybe it was not consistency.
Maybe the system was fragile.

If a system needs your best self every day, it is not built for real life.
Real life includes tired days, messy weeks, and low motivation.

I am not anti-system.
I just do not want fragile ones.

I do not want systems that become guilt machines.
I do not want systems that require constant optimization to survive.

I want something that blends into life.
Something that still works at 60 percent.
Something that survives boring weeks, because most weeks are boring.

And if you are trying systems, rebuilding them, tweaking setups, starting over, that does not mean you are lazy.
It means you care.

Lazy people do not reflect.
They do not rebuild.
They do not keep trying.

The issue is often not effort.
It is architecture.

This channel is not about optimization for optimization's sake.
It is about building things that survive:

• software
• habits
• money systems
• life systems

Not built for perfect weeks.
Built for real life.
Built for tired days.
Built for when motivation dips.

Built to bend, not break.

And mostly: built to survive past month three.
Because that is the real test.
Not how it feels at the start, but what is still standing when the novelty is gone.

Opening (0:00-0:45)

So before anything...
this isn't a tutorial.
I'm not an expert.
I'm not teaching anything.

(pause)

I'm just going to show you how I'm trying to use AI day to day.

And I'll be honest - I'm not very good at it yet.
It's messy.

(pause)

So this might be... kind of boring.
Because it's not a highlight reel.
It's just one developer - and one person - trying to keep up.

(pause)

This isn't how you should use AI.
It's just how it fits into my life right now.

---

Why I Use It (0:45-2:10)

And I'm not using it because AI is cool...
or because I want to brag about it.

(pause)

Honestly, I don't even talk about it that much in real life.
Because I'm always a little worried people will think I'm becoming reliant on it.

(pause)

But the truth is...
I use it like a backup.
Something that helps me move... when I normally stall out.

And that's actually very "Slow Builds."

(pause)

I'm not using AI to go faster in a hype way.
I'm using it to remove the friction...
so I can slow down where it matters.

(pause)

It makes it look like I'm speeding up...
but what's really happening is it gives me time back.

Time I can put into the parts that actually matter.
And it helps with the parts I struggle with.

(pause)

And sure - for someone else, it might be the opposite.
They might use it differently.
But for me... this is what it is right now.

---

The Speed of Change (2:10-4:15)

And part of why I'm using it...
is because I don't think what we see today is what it's going to be.

(pause)

It's changing fast.
Like... ridiculously fast.

I watched a video the other day where someone tried to explain it like this:

(pause)

We're used to new iPhones once a year.
Maybe every six months.
We at least have time to learn the thing... before the next one shows up.

(pause)

But AI isn't moving like that.

The idea was...
instead of humans iterating on it slowly...
it's the system iterating on itself.

(pause)

So it's not years.
Or months.

It's weeks.
Days.
Hours.
Minutes.

(pause)

And you can feel it.

I have a friend at work who said,
"yeah, I tried this... it wasn't that good."

And I asked him when.

(pause)

It was like three months ago.

And I'm sitting there thinking...
AI this morning is not the same AI it was three months ago.

(pause)

It's already better.

And that scares me.

(pause)

Like... actually scares me.

---

What Scares Me (4:15-6:15)

Not in a sci-fi way.
Not in a Terminator way.

(pause)

Although... who knows.

But what scares me is how unstoppable it feels.

You can't really "cut the cord."
It's distributed.
It's already out there.

(pause)

And I do think governments should be involved somehow...
I just don't know what that looks like right now.

(pause)

And I'm not even thinking about my generation as much.

I'm thinking about what this does over time.
A generation... two generations... down the line.

(pause)

Because right now, a lot of the people holding the keys...
management... leadership...
they're nervous too.

They might not say it.
But you can tell.

(pause)

And they're not going to blindly trust it.

Which is why I think for now...
there's still a place for senior developers, architects, product people...

Because companies still want humans to review.
Humans to decide.
Humans to own responsibility.

(pause)

But the people coming up behind that layer...
they're going to build new things.
And that part is exciting.

(pause)

...okay. I'm getting off topic.

Let me bring it back.

---

Where I'm At Personally (6:15-7:35)

I don't feel like I know what I'm doing at all.

I'm overwhelmed.
I feel behind.

(pause)

Every day it's something new.
New tools. New agents. New "this thing can run your life."

"Give it your credit card. Give it your login. Let it handle everything."

(pause)

That freaks me out.

But it's happening fast.

(pause)

And right now... my focus is building my own setup.
A new server.
A place where I can start running agents... for my projects... for my workflow.

I'm not trying to master AI.

I'm just trying to not be scared of it.

(pause)

I know it's impossible to fully keep up...

I just don't want to fall so far behind that I wake up...
and it feels like I'm in another country.

(pause)

I want to stay sane enough...
to keep moving through it.

---

What I Use It For (7:35-10:30)

Most of the time my AI use starts with confusion.

Messy thoughts.
Half-formed ideas.
Things rattling around in my head.

(pause)

I just dump it in.

And whatever comes back... comes back.

(pause)

Not always for answers...

More like... structure.

Reframing.
Different angles.
Steps forward.

(pause)

Especially for ideas.

Instead of doing hours of research to figure out:
is this feasible?
legal?
ethical?

I can throw the rough idea in...
and get a starting point back.

(pause)

And honestly... I've been pleased with what I get.

---

Prompts + "AI to Prompt Another AI" (10:30-12:30)

One thing I learned pretty fast is... prompts are the whole game.

(pause)

Like... the difference between spending five dollars...
and spending thirty cents...

is often just the prompt.

(pause)

Claude is expensive for coding.

So sometimes I'll use ChatGPT first -
just to build a better prompt for Claude.

I'll use one AI to write the prompt...
then paste it into the other.

(pause)

And that sounds silly...
but it saves money and saves time.

(pause)

I even built a little thing for myself where I can dump messy thoughts...
and it turns them into a structured prompt.

Code prompt.
Research prompt.
Personal prompt.

And it'll even tell me where to use it.

(pause)

Because if the system wants a prompt...
why not use it to help build the prompt?

---

Communication + Work Context (12:30-15:00)

And this part matters to me because...
I've always struggled with communication.

(pause)

I've done consulting for years.
I can figure out what to build.

But translating requirements...
decoding expectations...
turning feedback into something clear...

That's always been hard for me.

(pause)

So now... if I'm confused about a Jira ticket...
or code review feedback...
or what someone actually wants...

I drop it into AI.

(pause)

And it helps me see:

"here's what the manager is expecting."
"here's what the requirement actually says."
"here's what your code is doing."
"here's what the feedback means."

(pause)

That's not magic -
but it's a huge relief.

---

Family + Hard Conversations (15:00-17:00)

I also use AI for communication outside of work.

Texts.
Hard conversations.

(pause)

Not to avoid people.
Not to outsource emotion.

Just to pause.

(pause)

I'll explain the situation...
give a bit of history...
and draft what I want to say.

And I'll ask:
does this sound harsh?
does this escalate?
how would I say this calmer?

(pause)

And a lot of the time the output doesn't sound like me.

I don't copy-paste it.

But it still helps me see the situation clearer...
and respond slower.

---

Close (17:00-18:00)

So yeah... this is how I'm using AI right now.

Messy.
Practical.
Unfinished.

(pause)

I'm not trying to master it.

I'm just trying not to ignore it...
and not be scared of it.

(pause)

And honestly -
the better I get at using it...
the more it lets me slow down in the rest of my life.

(pause)

So... it belongs here.

Hopefully we all get through this...
and AI makes our lives better... not worse.

Hey, welcome to Slow Builds.

So this one's going to be a little bit different.

So this channel was really...

I have an idea to go through what AI told me would be anchors.

So like their family, investing, coding, life.

Just the main topics.

And we have 52 of those queued up, basically.

at least the most...

idea framed. And we had the also the idea of adding in, they called it like a bridge

video, which would be examples of what I'm doing, what I'm working on, how I use the

things that I talk about from time to time, maybe what I'm investing in, especially reading,

there'll be a lot of references to books, almost like little quick book reviews. But

I think that's what we're gonna decide what these are called so they'll come out not

Whatever I feel I want to say something

So at the moment

So

so this one really is gonna be maybe Tesla Elon and what I think I saw might be happening and

When he was at Davos, I noticed

He started commenting about the Sun because he was asking about solar panel solar power

And he was asking about the EVs and the robots and stuff like that

But he can he mentioned like the Sun and how much power

Can be generated and I think he mentioned like enough the power all of China

Which is pretty insane and then he did mention

uninterrupted sunlight

So ding ding

What does he have? He has the rocket ships. He has the satellites

So for him it's not that big a deal so you start thinking about it, it's like he has these plans to

Do satellite to come out for Starlink, which are super powerful

One friend mentioned how he feels the transmission time delays, but I think

At my level and my friends level

There's things that are being developed and changed that we don't know

And I believe Elon has the right people in place to help him figure these things out

So if he's throwing up the rocket ships and then he's throwing up the massive solar panels and he wants to start

He has grok and AI and he wants to start building

These chips and I really believe if he can't find the right supplier. He is going to make him

Himself and it's probably already in the work somewhere

Prototypes and whatever else because he the numbers he's talking are massive

Even taking off the Tesla car to earn in the robots and how many wants to pump out which means he needs the chips

Which means he's the power he needs da I he needs everything. So when you think about it

With the and with the Starlink involved he has it all he has all the pieces in place

Throw up those satellites have him directly pointed at the Sun. They're collecting all the power. He's got

Let's just say what he's going to do data centers in space because what happens free energy

That's one of the biggest cost. The other problem is the heating wall in space. There's no problem with that

So he can have these

Super data centers up in space floating around processing all this data. We're sending up requests and whatever

It's caching everything and then it's star link connected to the car connected to the robots connected to your laptop your computer your phone

Whatever. I still think he is working on a phone

It's just too big and I really believe he I don't think he thinks a little ways down the road

I think he thinks long long term, but hoping it happens faster than it does because he tries to push people which

It comes off

Rude and mean and whatever, but I think his goal is just

Get the Mars

and to make us the smartest

Civilization is possible. I

Believe a lot of what he says. I think a lot of it does come across as I

I don't want to say the crazy word, but it kind of feels that way.

But in the hard-hating time, the crazier the idea, it just seems to be that's what people

are doing and that's why it works.

It's like living in the Jetsons.

So as bad as it is to have one man with all that power, I do believe someday I'm going

to wake up and my Tesla stock is now going to be a combination of all of them.

The biggest company in the world of history.

runs everything, everything runs off of it. It's kind of scary to have that much

power but hopefully there's regulations and things in place. And the other thing

is he wants to get the Mars. He wants to give us a chance to live. He wants

to build civilization right I think or at least in the way he believes it should

be run. I don't think anyone's gonna stop him. I don't think no matter what he does I

I think he's the only one pushing the envelope farther and farther ahead.

He's trying to get there quicker because I think he wants to see it in his life.

And if he's able to do that, then it helps all mankind really.

In many ways, I can't even think about him, so I'm not even going to go there.

But I believe no one's going to stop him.

I believe he's going to be able to keep doing what he's doing.

People want to put up with it.

People want to complain.

People want to buy his products.

Worse comes to worse.

Government funded.

Private funding.

I think people are going to let him run this course in hopes that it turns into what mankind

possibly needs.

This is a true random.

This is a rambling, like the best of them.

It's like sitting around with the guys and just, what could happen?

What's a crazy idea?

And that's what I feel this one's turning into.

And that's okay, like there's no script there.

So hopefully this one, I don't need to edit it.

I haven't edited anything yet.

Everything's been a one shot deal.

And I feel I wanna do more, if I post this,

and I think I might after I rewatch it,

make sure I don't say anything too crazy.

I like doing the random links.

I have like, I have an idea I wanna do,

I really want to do it now, but like with Nike,

I want to pop something out for that.

The autonomous cars.

Why I'm very, very bullish, bullish on Uber right now.

And why my strategy has changed a lot.

Yeah, slow builds.

I think all these are slow, like you invest it, forget it.

It's good volatility is through the roof on these.

But I believe there's missing pieces that make them slow, slow build.

It's like you put the money in and you live with it.

It's like Bitcoin, you know, you just, you kind of ignore the news.

You follow it because you enjoy it and you're, you're invested in it.

But in the end, it's more, you got to go with your gut.

Like another one that I've got my kid to invest in and myself, Rivian.

I honestly believe that they have a great chance, but it all comes down to cash flow.

How long is that runway for them?

Can someone keep them alive?

Do they want to keep them alive?

But again, rambling, which is the purpose of it.

So hopefully you like this.

I would love to do more of these actually because I feel more comfortable doing this.

So we'll see what happens.

All right, thanks.

and leave some comments. I need to know if someone's actually watching this. It's

reaching a point that like I said I wanted to give up but I when I commit

to something I usually try to push through. I am pumping them out a little faster

than I was expecting because new it's new but if I know I'm gonna keep to my

schedule. It gives me a... I don't know, smart goals. I have small little attainable goals

along the way. Smart goals is another one that I want to put out. But yeah, let me know

if this is interesting to anyone. If I'm way off pace, do I even have a chance here? But

thank you.

0:00–0:25 — OPEN (settle in)

The first video was the what.
What this channel is about.
⏸ (2 sec)

The second video was the why.
Why I want to do it.
⏸ (2 sec)

I don’t know if I had to do it —
but I know I want to.
⏸ (3 sec)

So when you put that together —
what, why, when, where, how —
this video is the when, the where, and the how.
⏸ (3 sec)

And just to be clear up front —
I’m still figuring this out.
⏸ (2 sec)

⸻

0:25–1:20 — WHEN (cadence)

So starting with when.
⏸ (2 sec)

The goal is one video a week.
Maybe twice some weeks, if I can.
⏸ (2 sec)

In theory, that’s 52 videos a year.
I actually have about 52 ideas already.
⏸ (2 sec)

I don’t know if they’ll all make it.
⏸ (2 sec)

But the idea here is consistency over quality —
which… you can probably tell already.
⏸ (3 sec)

This isn’t a promise.
⏸ (2 sec)

It’s an intention.
⏸ (3 sec)

⸻

1:20–2:05 — WHEN (origin of the idea)

But when isn’t just about a schedule.
⏸ (2 sec)

This idea didn’t start all at once.
⏸ (2 sec)

It’s been sitting in my head for a while.
⏸ (3 sec)

Watching my kids do their thing.
Watching how fast everything is moving.
⏸ (2 sec)

And noticing what actually seems to matter online right now.
⏸ (3 sec)

⸻

2:05–3:00 — WHERE (physical)

That brings me to where.
⏸ (2 sec)

Physically — it’s this room.
⏸ (2 sec)

I moved things around a bit.
I’m very aware of what’s behind me.
⏸ (2 sec)

The acoustics aren’t great.
The lighting isn’t great.
⏸ (2 sec)

It’s quiet…
⏸ (1 sec)
which is actually kind of scary.
⏸ (3 sec)

I think nobody can hear me.
⏸ (2 sec)
I hope nobody can hear me.
⏸ (3 sec)

I’m not comfortable filming outside yet.
I’m not ready to just grab my phone and talk.
⏸ (2 sec)

So this room isn’t ideal —
⏸ (2 sec)
it’s just the place where I’ll actually show up.
⏸ (3 sec)

⸻

3:00–3:45 — WHERE (mental)

But there’s another where.
⏸ (2 sec)

Mentally, this came from watching my kids.
⏸ (2 sec)

They’re adults now.
⏸ (1 sec)

One is building in public —
trading, YouTube, documenting.
⏸ (2 sec)

The other makes a living from art.
⏸ (2 sec)

Both are putting real work out there.
Not polished.
Not optimized.
⏸ (2 sec)

Just… real.
⏸ (3 sec)

⸻

3:45–4:50 — HOW (AI + stance)

That’s where the how comes in.
⏸ (2 sec)

AI is moving fast.
⏸ (1 sec)

People argue about it constantly.
⏸ (2 sec)

“Is this AI?”
⏸ (1 sec)
“AI is garbage.”
⏸ (2 sec)

It feels a lot like the early internet.
⏸ (3 sec)

Where I land is pretty simple.
⏸ (2 sec)

I use AI.
⏸ (1 sec)

I don’t use it “right.”
⏸ (1 sec)

I’m not an expert.
⏸ (2 sec)

But it helps me move.
⏸ (1 sec)
It helps me think.
⏸ (1 sec)
It helps me build.
⏸ (3 sec)

⸻

4:50–5:40 — HOW (slow vs fast)

I see a lot of people using it to pump things out.
⏸ (2 sec)

Hype.
Flash.
Volume.
⏸ (3 sec)

What I’m interested in is different.
⏸ (2 sec)

Using AI to speed up the parts that don’t matter —
⏸ (2 sec)
so I can move slowly where it does.
⏸ (3 sec)

Structure.
Organization.
The boring parts.
⏸ (2 sec)

It gives me a foundation —
⏸ (2 sec)
and then I decide what actually stays.
⏸ (3 sec)

⸻

5:40–6:20 — WHAT STILL MATTERS

I don’t think AI replaces everything.
⏸ (2 sec)

Doctors still matter — assisted.
⏸ (1 sec)

First responders still matter — assisted.
⏸ (2 sec)

Storytelling still matters.
⏸ (1 sec)

Taste matters.
Perspective matters.
Presence matters.
⏸ (3 sec)

Even if most content becomes generated —
⏸ (2 sec)
people still feel what’s real.
⏸ (3 sec)

⸻

6:20–7:00 — CLOSE (land it)

So this channel is really about
moving slowly in fast times.
⏸ (3 sec)

I don’t know where this goes.
⏸ (2 sec)

I’ve already doubted it.
⏸ (1 sec)
I’ve already lost interest more than once.
⏸ (3 sec)

But if I don’t show up —
⏸ (2 sec)
I’ll never know.
⏸ (3 sec)

So I’m giving it a chance.
⏸ (2 sec)

I’m not promoting it.
I’m not pushing it.
⏸ (2 sec)

I’m just putting it out there —
⏸ (2 sec)
and paying attention while I do.
⏸ (4 sec)

Thanks for being here.

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.

What Is Slow Builds?

Opening (0:00–0:45)

Hey — welcome to Slow Builds.

I want to start by saying this isn’t a trailer.
This isn’t a highlight reel.
And it’s definitely not me teaching anything.

I’m not an expert.
I’m not ahead of the curve.

I’m just documenting what I’m building
and what I’m working through
as I go.

(pause)

Most of what you see online is either hype
or hindsight.

This is neither.

This is the middle.

---

What “Slow Builds” Actually Means (0:45–2:00)

When I say slow builds,
I’m talking about long-term work.

Code.
Money.
Habits.
Health.
Responsibility.

Things that compound quietly over time.

(pause)

No shortcuts.
No pretending it’s exciting all the time.

Just showing up —
even when it’s boring,
unclear,
or slower than you’d like.

I’m not trying to optimize life here.
I’m trying to stay consistent
without the noise.

---

What Shows Up on This Channel (2:00–3:30)

I work in software.
I build side projects.
I use AI as a tool — not as hype.

I invest steadily.
Mostly boring stuff.

I train,
try to stay healthy,
and keep some structure in my life.

And sometimes I’ll talk about
family,
trade-offs,
and responsibility —
when it’s relevant.

(pause)

There isn’t a polished content plan behind this.
It’s centered on whatever I’m actively
working through at the time.

---

What This Channel Is Not (3:30–4:20)

This isn’t motivation.
It’s not productivity theater.

I’m not here to perform discipline
or sell outcomes.

(pause)

Some weeks will be useful.
Some weeks will be quiet.
Some weeks I’ll still be figuring things out.

That’s intentional.

---

Who This Is For (4:20–5:05)

This probably isn’t for everyone.

If you’re looking for shortcuts,
big promises,
or fast results —
this channel will feel slow.

(pause)

But if you’re building things quietly,
tired of performance,
and more interested in process
than polish —

there’s probably something here for you.

---

Close (5:05–5:30)

I’m not teaching from a finished place.
I’m documenting while I’m in it.

If that’s useful,
you’re welcome to stick around.

(pause)

Most of what I’m building
doesn’t look impressive —
but it lasts.