Seeing Life As Unfinished, Not Broken [Raw Session]

00:00 — Seeing Life as Unfinished, Not Broken

Hey, welcome back to Slow Builds.

Lately I’ve been thinking about how easy it is to look at your own life and assume something is wrong, just because everything kind of looks unfinished.

Nothing feels like it’s really falling apart. Your life isn’t ruined. It’s not hopeless.

There are just so many unfinished projects and tasks that you want to get done, and it becomes overwhelming in a way.

I think that distinction matters more than we give it credit for.

Because a lot of the time, when we look at other people, we see the finished version, or at least the version they want us to see.

The clean version. The edited version. The part where the decision already worked out.

The app already launched. The business already makes money. The debt is already gone. The body already changed. The system already makes sense.

When we look at our own life, we see the scaffolding.

We see the browser tabs open, the note app full of half thoughts and unfinished ideas.

We see the budget that still has all kinds of gaps in it, and it’s not being met or finished yet, and not being followed.

The fitness plan that worked for three weeks, and then it got interrupted. You got tired. It was vacation, work, sick. It just didn’t follow through, but the plan is still there.

You see the project that’s still missing the feature that you want to get rolled out, or the last couple of bugs that need to be tested and tightened up.

We see the video idea. This one is pretty good for me. It sounded clear in my head, but it comes out messy when I try to talk through it. I get lost. I’m going to get lost in this one too, guaranteed.

Because we are inside it, it can feel like evidence that we are falling behind.

We’re not where we want to be, or we compare ourselves to where everyone else might be.

But maybe it’s not always that.

Maybe some parts of life are not broken.

Maybe they’re just not finished yet.

02:12 — Some Things Really Are Broken

I don’t mean that in a motivational way.

I don’t mean everything is secretly going to be great. It’s going to turn out just the way you want it.

Some things really are broken.

Some decisions really do need to change. Habits really are damaging. Some relationships, systems, jobs, projects, and regular routines need to be looked at honestly and revisited, removed, tweaked, or just started over.

But I think we also create a lot of extra pressure by treating every incomplete thing as a personal failure.

That is something I keep running into with software, money, health, this YouTube channel, all kinds of family stuff, and especially with AI.

I always feel like I’m falling behind. Touching on that, I actually think the system is built in an odd way, and maybe falling behind is part of the process anyway. We can get to that in a different one.

We’re just trying to build a life that feels a little more intentional than it did before.

There are so many areas where the work is happening, but the result is not clean yet.

And when the result is not clean, it is tempting to think the work does not count.

I think that is a wrong way to look at it.

03:35 — Software Starts Ugly

One thing software has taught me is that almost everything useful starts very, very ugly.

You think you understand what you’re building. Then you actually start building it and suddenly the clean idea in your head turns into a pile of edge cases, incomplete prompts, bad links, bad buttons, errors, incomplete databases, missing flows, and a page that looks half done.

Then the user doesn’t use it the way you expected it. There’s no validation. It’s all kinds of mess.

But that stage is still not garbage.

That stage is the point where the idea starts becoming real.

Reality is where the clean version gets challenged.

That is true in code, and I think it’s true in life also.

A lot of plans look great before they touch reality.

A money plan looks good before the car breaks, or in my case, the deck breaks, the fence falls down, or the car needs to be fixed.

Fitness plans look good before you get a bad night’s sleep and don’t want to get up early. Or you plan on running outdoors and it’s raining, too windy, or too cold.

A content plan looks good before you actually have to sit down after work and record something.

A family boundary looks obvious until real emotions show up.

An app idea feels simple until you have to think about onboarding, security, privacy, payments, support, data privacy, and everything anyone actually cares about.

Once reality hits, we often assume the plan failed.

But maybe the first version just met production.

That is probably the best way I could put it.

A lot of life is your first version hitting the road. Wheels hitting the road. Foot on the gas. Production is messy.

There are real users, real bills, fatigue, interruptions, old habits, people with different needs, and always limited time.

There is your own mood too, which is not always as reliable as you wish it was.

So when something gets messy, it does not automatically mean the whole thing is wrong.

It might just mean you’re finally seeing what needs to be adjusted.

06:16 — Money Does Not Become Simple

That has been a useful way for me to think about a lot of things, especially money and investing.

I used to think of money more as a final state.

At some point you’re supposed to have it figured out. You save enough, you invest enough, you make enough, you can finally relax.

But I don’t know if it really works that way.

At least it has not felt that way for me at all. Not even close.

There’s always another layer.

You pay off one thing, then notice another thing.

You increase your income, then taxes become more visible.

You start investing, then realize you have to manage the risk that goes along with it.

You start paying attention to the news and world events, and at the same time notice how that affects your ups and downs.

You buy a house, maintenance shows up. People don’t realize that owning a home is not cheap.

You own a rental, people become part of that equation. Sometimes it’s family, which gets real messy real quick. Or maybe it’s people that know how to game the system.

But sometimes you luck out. I’ve had it every single way.

You try to help family, then realize helping and enabling are not the same thing.

You start thinking about retirement, then you have to think about health, kids, timing, inflation, and how long life actually is.

So even when things improve, they do not necessarily become simple.

They just become more detailed.

And I think that is part of progress people do not talk about enough.

Progress does not always make life feel lighter right away.

Sometimes progress gives you better problems, bigger problems.

That sounds negative, but I don’t mean it that way.

It’s just more honest.

08:11 — Problems Change Shape

When you’re broke, the problem might be survival.

When you start earning more, the problem might become stewardship.

When you’re unhealthy, the problem might be just moving.

When you start getting healthier, the problem might become sustainability, continuing it.

When you have no projects, the problem might be boredom and wasted potential.

When you start building things, the problem becomes focus, maintenance, shipping, and deciding where to place your attention.

So the problem does not disappear.

The problems change shape.

They morph into something else.

If you expect progress to feel like the end of problems, you might misread the next stage.

You might think, why am I still dealing with friction? Why am I still so tired all the time? Why do I still never feel done? Why is there uncertainty in everything I think about or touch or get involved in?

Maybe the answer is because done was never really the deal.

Maybe life is mostly maintenance and adjustment.

It doesn’t sound flashy, but it feels very true.

You do not build a body once. You do not build a marriage once. You work on your body. You work on your marriage.

You do not build a career just one time. You’re constantly moving through your career.

You do not build a financial life once. There are always ups and downs.

You do not build the software once. You build, maintain, fix, rethink, and sometimes tear it down and start over.

If you’re waiting for the moment where everything is finally locked in and complete, you might spend most of your life feeling like you’re failing, even when you are actually making progress.

That is the part I’m trying to be more careful with.

10:12 — The Big Pile of Everything Undone

Because I can do this thing where I look at everything that is not done and mentally turn it into one big pile.

The app is not finished. The YouTube channel is way too small. The house needs work. Vehicles. Fitness. Money. Family. Business. All the automation stuff I want to build with AI. All my notes are scattered. Taxes. Accounting. Organization.

I’m getting overwhelmed just going through the list and feeling like so much of my life is undone.

When you stack it all together, it feels like complete chaos.

But if you separate it out, some of it is just normal life.

Some of it is active construction.

Some of it is waiting for the right session.

Some of it is not urgent at all.

And a lot of it is not even a real problem. It’s just problems we make on our own. It does not need my attention.

Sorting these things makes a difference mentally, emotionally, and even physically to some extent.

Because when everything unfinished feels equally urgent, you end up exhausted before you even start.

You’re like, why even bother?

You do not know whether to fix the app, organize the money, clean the house, record the video, or go for the run.

I had to go for a run. I had just finished a call and wanted to try to get this video out. Trying to knock off little things makes a big difference.

But even then, I’m going to go back on this and it’s not going to be done. I’m still going to feel incomplete.

So your brain treats the whole thing as danger.

That is where I think a lot of people get stuck.

Not because they are lazy. Not because they don’t care. But because they’re caring too much.

There are too many loops without knowing which one actually matters today.

Which one is the most important one to tackle?

12:22 — What Slow Building Actually Means

I think this is where slow building helps.

Not because it makes everything easier. It does not.

Nothing gets easy.

But because it gives you permission to stop pretending everything needs to be solved at once.

Slow building is not about moving slowly for the sake of moving slowly.

It’s more about refusing to panic just because something takes time.

It is saying, okay, the thing is not finished. What is the next honest piece?

Not the perfect piece. Not the impressive piece. Not the piece that makes the whole thing look great. Not what you envision in your mind.

Just the next real piece.

That could be one feature, one walk, paying off a bill, having that hard conversation, spending an hour cleaning, putting some time aside and doing that.

Get one video recorded. Just record it. Don’t worry about editing it. Don’t worry about anything else. Just record it and get it ready for the next step.

There’s a lot of dignity in that.

Even if it does not look like much from the outside.

Maybe that is why I keep coming back to this channel overall.

I’m not trying to present the finished version.

I do not think I could even if I wanted to. I really can’t because I don’t know how to do videos. I don’t know how to do anything. That’s why they’re all unedited raw sessions.

I mix up. I mess up. You see it.

And that’s okay because that is where most people actually live.

They live in those messy moments.

14:06 — Most People Are in the Middle

Most people are not in the launch video.

Most people are not in the before-and-after picture.

Most people are not in the final chapter.

They are somewhere in the middle of 20 different things.

Trying to make money, stay healthy, keep the relationship intact, understand AI, keep up without getting swallowed up by everything, and keep their head above water.

They’re trying to build something useful.

Trying not to waste their time, trying to be less reactive, trying to become a little more stable.

And it’s easy to think, once I get this part handled, then I can start.

Once the house is clean, the schedule is better, the app idea is cleared out, I have more energy, the weather changes, there is less stress about money, I understand how to use the tools, life calms down.

But it never does.

I’m not sure life ever calms down. Not in the way you imagine.

You get moments. It changes. Some things get easier. Other things become more complicated.

At the same time, you either build inside the unfinished life you have, or you keep waiting for a clean starting point that is never going to show up.

You just have to get up and do it.

It sounds simple, but it’s hard to accept because an unfinished life does not feel very inspiring.

It feels inconvenient.

You have to build around appointments, work, family, bad decisions, repairs, fatigue, your own inconsistencies.

Around the fact that some days you just do not feel like the person you thought you were becoming or supposed to be.

That can mess with your identity and your mental state, because we like to believe progress should make us more consistent and bring us to that vision of where we expect to be.

But sometimes progress reveals how inconsistent we still are.

16:10 — Returning Faster

You start running, then miss a week.

You start eating better, then have a bad stretch.

You start building an app, then avoid it.

You start making videos, then question the whole thing.

You start using AI, then feel overwhelmed by how much there is to learn and how much other people are doing it differently than you are.

You start organizing money, then make impulse purchases or unexpected purchases show up.

The old version of you wants to use that as proof.

See, you’re not really changing.

But I do not think that is always true.

Sometimes change looks like returning faster.

Not never slipping.

Not never drifting.

Not never getting tired.

You notice sooner. Come back with less drama. Make the next useful move without turning the mistake into your entire identity.

That is another place where software gives a decent metaphor for me.

A bug does not mean the entire application is worthless.

It means something needs to be inspected.

Maybe the logic is wrong. The input was unexpected. The assumption that was made when it was built was incorrect. There was bad test coverage.

We do not delete the entire project every time something breaks.

At least you shouldn’t.

You debug it. You isolate the issue. You fix what you can. You learn something about the system overall, and then you keep going.

But with ourselves, we are often much harsher.

One bad day becomes, I have no discipline.

One awkward video becomes, I’m not good at this at all.

One missed workout becomes, I always fall off.

One missing month becomes, I cannot manage money.

One unfinished project becomes, I never finish anything.

That is not analysis. That is just a bad error message.

It tells you almost nothing useful.

18:19 — Less Shame, More Inspection

A better message would be more specific.

What broke?

Where did the system fail?

Was the goal too vague?

Was the schedule unrealistic?

Was the environment working against me?

Was there too much friction?

Were you tired?

Did you get enough sleep?

Were you avoiding something because it was unclear?

Or did you just not want to meet the conflict or friction that came along with it?

Did you even actually care about the thing?

Or were you just chasing the idea of being the kind of person who does that thing?

Those questions are more useful than shame.

That’s probably one of the biggest shifts I’m trying to make.

Less shame, more inspection.

Not in a soft way. Not in a pretend everything is fine way. But in a practical way.

Shame is usually bad at system design.

It makes you want to hide, quit, or overcorrect.

Inspection gives you information, and information is something you can work with.

That applies to AI today also.

A lot of people are trying to figure out where they fit now.

Developers are wondering what coding even means when AI generates huge chunks of it in fractions of the time.

Creators are wondering whether anything they make will stand out compared to the constant AI junk thrown out there, and how realistic that junk is becoming.

Businesses are wondering which tools matter and which ones are noise.

Regular people are trying to understand if they are falling behind the curve. Are they part of that restructuring process that’s going to happen within their business, their life, and the whole thing?

It feels unfinished because it is unfinished.

20:07 — Living During the AI Shift

We’re not living after the AI shift.

We’re living during it.

That means a lot of our conclusions are probably very early.

Some of the fears are justified. Some excitement is justified. Some of the predictions are very wrong.

I’ve talked about this before. Jobs are going to change. Career paths are going to change. Some people gain access they never had before. Some people will get extremely overwhelmed and anxious.

Some tools are going to disappear. Some workflows will become normal so quickly we forget they were new, or that we even use them because they are automated behind the scenes.

In that kind of environment, trying to have a perfectly settled opinion might be the wrong goal.

Maybe the better goal is to stay engaged without pretending to know the full shape of it yet.

That’s another form of living with unfinished systems.

You can use AI without making it your whole identity.

You can be cautious without being frozen.

You can be optimistic without being naive.

You can admit the tools are powerful without pretending they solve every human problem.

You can build with them and still care about understanding what is happening underneath.

That balance is very hard.

I think a lot of people are tired because they’re trying to resolve something that is not ready to be resolved yet.

They want the final answer.

Is this good or bad?

Is this opportunity or is it threat?

Is this the future or is it just all hype?

Is this freeing people or making them more dependent?

The annoying answer is probably yes to parts of all of it.

Which means we have to live in the tension for a while.

And that is extremely uncomfortable, but it’s also real.

22:05 — Judgment Takes Longer Than Information

Not everything important gives you a clean answer right away.

Sometimes you have to keep observing, keep testing, keep adjusting, keep asking better questions.

That is not weakness.

That is how you build judgment.

And judgment takes longer than information.

Information is cheap now.

AI can give you information instantly, but judgment still has to develop through contact with reality, through mistakes, repetition, noticing patterns, and seeing what actually happens when an idea leaves your head and enters the world.

That might be one of the reasons I still care about building slowly.

Because slow building creates contact with reality.

You cannot just live in the imagined version forever.

At some point you have to record the video. Push the code. Send the invoice. Make the phone call. Do the workout. Check the numbers. Have that conversation.

Then reality gives you feedback.

Usually not as cleanly as you hope, but it gives you something.

Then the question becomes, can you keep working with that feedback without making it too personal?

That is hard for me.

I think it’s probably hard for a lot of us because feedback can feel like judgment.

A video cannot perform very well and it feels like people rejected that idea.

A dislike hurts.

An app has no users and it feels like the project is pointless.

A plan slips and it feels like you failed.

A conversation goes badly and it feels like nothing can change.

But sometimes feedback is just data.

Not always. Sometimes it does mean something serious.

But not every weak signal deserves a dramatic story.

Sometimes the video title was unclear.

Sometimes the app needs better onboarding.

Sometimes timing was just wrong.

Sometimes you’re tired.

Sometimes the idea needs more time.

Sometimes the thing is not ready yet at all.

And sometimes maybe it’s not worth continuing.

But you usually need calm attention to tell the difference.

Panic is not very good at making that call.

24:15 — Unfinished More Than Broken

That is why I like the phrase unfinished more than broken.

Broken makes me want to either fix everything immediately or throw the whole thing away.

Unfinished makes me ask what stage it is in.

Early? Stuck? Neglected? Waiting? Is this actually done enough?

That last one matters too, because some things stay unfinished because we keep moving the finish line.

A video could always be better. An app could always have another feature. A budget can always be a little more optimized. The room can always be cleaner. The plan can always be more complete.

At some point, unfinished becomes an excuse to avoid releasing, deciding, or accepting.

So I’m not saying unfinished means harmless.

Sometimes unfinished is where we hide, and that is worth being honest about.

There’s a difference between a slow build and avoiding a build.

A slow build still has movement.

It may be small. It may be inconsistent at times. It may pause when life gets heavy, but there’s still some contact with the work.

An avoided build becomes something we only think about.

We talk about it. Research it. Rename it. Plan it. Imagine it. But we never really touch it.

I’ve done that too.

Sometimes planning feels like progress because it’s cleaner than execution.

Execution creates evidence.

Planning creates possibilities.

Possibilities feel better because it has not failed yet, but possibility also does not become anything unless it gets tested and started.

That is a tension I keep noticing.

I do not want to rush everything, but I also don’t want to use slow building as a polite way to avoid shipping.

So maybe the question is not, is this finished?

Maybe the question is, is this alive?

Is there still movement here?

Does it have my attention?

Is there still a reason to continue?

Is the next step small enough that I can actually do it?

That feels more useful, because some things in life will be unfinished for years.

26:20 — Keeping the Important Parts Alive

Your health is never finished.

Your finances are never complete.

Your relationships are never finally finished.

They are all still living things.

Your skills are never learned. You’re always learning new ones.

Your understanding of the world keeps changing as the world changes and you get more experience and more knowledge.

Even your identity changes from time to time.

It’s always moving.

So maybe the goal is not to finish your life.

Maybe the goal is to keep the important parts alive. To maintain what matters, repair what you can, stop caring about what no longer belongs to you, and build something slowly enough that it can actually become part of your real life, not just your fantasy life.

That is where I think this matters.

Because if you believe your life is broken every time it is unfinished, you will constantly feel behind.

When you constantly feel behind, you start making bad decisions.

You rush. You compare. You buy things you don’t need. You chase shortcuts. You copy people whose lives are nothing like yours. You abandon things too early or cling to things too long because you don’t want to admit they’re not working.

Both can happen.

But if you can look at your life more honestly and say, okay, this area is unfinished but it’s not broken, then you can breathe a little. You can work with it.

You can make a smaller decision.

You can stop turning every open loop into a crisis.

That’s probably the point of this video.

Not that everything is fine.

Not that unfinished is always good.

Not that slow progress is automatically noble.

Just that we need better categories.

Broken. Unfinished. Neglected. Growing. Paused. Done enough. Not worth continuing.

Those are different things.

If we mix them all together, we make life harder than it already is.

28:15 — Living Inside the Build

For me right now, a lot of things are unfinished.

The channel is unfinished. The software ideas are unfinished. The way I use AI is evolving.

The money plan is better than it was, but there is no perfect final step or system to put in place.

Health is constantly ongoing. Family stuff is always complicated. Houses always need repairs. Vehicles always break down.

There are ideas I have not acted on yet.

There are habits I still have to protect and habits I have to undo.

There are days where I feel clear and days where I feel like I just reacted to whatever was in front of me.

But I do not think that means everything is broken.

It means I’m living inside the build.

Maybe that is where most of us are.

Not at the start or the finish. Inside of it.

Trying to keep enough awareness to not drift too far left or right.

Trying to keep enough patience to not quit too early.

Trying to keep enough honesty to not lie to ourselves.

Trying to keep enough humanity when reality shows us something.

That is not a clean story, but it might be a real one.

I think there is some comfort in that.

Not comfort as in everything works okay. Comfort as in maybe the mess does not automatically disqualify you.

Maybe the half-filled parts are not proof that you failed.

Maybe they’re just where the work still is.

Maybe the next right move is not to reinvent the whole life.

Maybe it is to pick one unfinished thing and touch it honestly.

Not solve everything.

Not become a new person overnight.

Just touch the work.

Look at it.

Look at it without flinching.

Ask what stage it’s in. Ask what it needs next. Then do that piece.

That is slow, but it’s not nothing.

Over enough time, not nothing can become quite a bit.

That is all I have for this one.

I’m still thinking it through, but the phrase that keeps sticking with me is maybe it’s not broken.

Maybe it is still being built.

It’s unfinished, and maybe that applies to more of life than we really think.

30:37 — Closing Note

Again, AI wrote this entire one for me.

I went through it. I did. I ad-libbed quite a bit.

It’s longer than I expected, but I think it’s a message that needs to be out there.

I like this message.

I use ChatGPT for a lot of these and I told it, take what I have and make me one. I want to see what came out of it.

I’m happy with that because it is unfinished and it’s a work in progress. That’s the way we have to look at things.

Small goals. Take a big goal and turn it into small ones. Knock those little ones out here and there. Be honest about it and celebrate the small wins, because those small wins lead to big victories.

Alright, thanks for watching.