It’s Rest Time
If you’re not resting, your work will reflect it. Next week is my rest-week and I’ll exhale, read, watch and like. This week was intense for me—good thing I stopped and actually looked at what got done
That gave me the motivation I needed.
I shipped something. Just a “skill” pushed it to GitHub—it’s live, done, not perfect, but done.
Did you ship something?
What’s up, I’m Clint. Built software. Led teams. Now a founder helping builders who are ready to make the leap but can’t quite see the path yet. Every post is one conversation closer to clarity on ownership, execution and momentum.
Progress IS a WIN!
If you did ship something, celebrate it—do it now, I’ll celebrate with you: Congratulations 🎉
Outside of daily context switching, the building chaos, the war and politics pulling at your attention in every direction—you have to give yourself credit.
Small wins matter. My skill shipped and that partnership I mentioned a few weeks back? It evolved. I’m now building a standalone app to help with accounting and bookkeeping during tax season.
A real problem, building a real solution.
That’s what happens when you stop pitching and start asking the right questions—a habit I’m still working on.
My project management app hit a good MVP stopping point. I’m actually using it every day without tweaking it—it fits my mental model on how I work.
It’s not finished, but finished enough to breathe, call it a phase and call it shipped too. WIN! 🎉
Yes, I had the feeling lol. The whole time, the urge was there—switch tools, add a feature, chase the new idea.
I actually wrote 2 articles about that exact situation and how I handled it—see below.
I needed balance—for my mental—so, I got out of the house, away from staring at my computer all week, and went to a networking event.
The room was full of technical leaders—VPs, CTOs, Directors, Engineering managers—all trying to figure out the same thing: What do we actually do with AI, and how do we get our teams to ship with it instead of just talk about it?
These are the people at big tech that solo builders think are ahead of them.
They’re not.
The solo builders are grinding at home—even on the weekends—figuring things out in real time, shipping and failing and shipping again—that’s the cutting edge.
The boardroom is scraping and “clawing” 🦞 to catch up to what you’ve been living every day.
Still think you’re behind?
The News Proves It
Here’s what caught my eye in the new: ~55,000 tech workers have been laid off in 2026 and most of them are engineers. Tech Layoff Tracker
I even saw a post on LinkedIn from a tech leader saying “We don’t need junior engineers anymore, we got AI.”
Wow 😳
The leaders are AI-biased, confused, displacing engineers and just lost.
So, the ones who figure out how to build, lead and ship, are going to be the ones who matter most in the next few years.
That’s us!
We’re all juniors in this
…And that’s who’s not behind.
In case you missed these from the last two weeks:
We Agree — You’re NOT Behind
You are capable and do feel stuck sometimes.
Take a break, pause then look at what you’ve accomplished in a week.
It shows you’re focused: one project, one track and one conversation closer
I’ve been on the software engineering and leadership track as a builder—with people and teams: see my LinkedIn
If you want to talk about it, join my chat, or send me a DM.
That’s exactly what I’m here for.
Thank you for supporting my work
If you want more—wanna explore how we can work together?
Clarity for the capable but stuck — 1 bite at a time.
— Clint
the measurement question is the hard one. execution had clear outputs — it shipped or it didn't. judgment shows up in what doesn't happen: the bad call that gets caught, the wrong output that doesn't make it through. that's harder to count, which is probably why it keeps getting undervalued until something breaks.
the boardroom vs. solo builder gap is real — and it's widening. the people declaring 'we don't need juniors anymore' are optimizing for the wrong thing. fewer engineers doesn't mean no engineers. the roles compress, the stakes go up, the ladder gets harder to climb — but the ladder doesn't disappear. what actually matters now is judgment: knowing when the AI output is wrong, not just that something is wrong. that's not a junior skill. it's the only skill that doesn't get automated away.