I have been thinking about fulfillment lately.
Not in the soft, poster-on-the-wall way. More in the practical, slightly uncomfortable way you think about it when you have been through enough career shifts to know that the shiny version of work is not always the honest version.
Jason Cohen wrote a piece called “Finding Fulfillment” that frames fulfillment around Joy, Skill, and Need. I am not going to summarize his article here. You should read it if that idea hits you at the right time.
For me, it was useful because it gave me a mirror.
Not an answer.
A mirror.
It made me look at the work I keep coming back to, the work I am good at, the work people actually need from me, and the work I am done compromising around.
Because at this point in my life, I am not trying to chase every impressive lane anymore.
I am trying to choose the work that is useful, hard, honest, and still mine.
I Am Built for the Middle of the Mess
If I am honest, I think I am built for wrangling chaos.
Not chaos for the sake of chaos. I do not enjoy dysfunction. I do not enjoy cleaning up avoidable messes. I do not enjoy people creating problems and then acting confused when someone has to fix them.
But I am good at stepping into complicated situations and translating them into something usable.
That might be agency operations. It might be AI tools and agent systems. It might be WordPress, automation, documentation, client communication, field reality, or a contractor who knows something is broken but does not have the words or time to explain it cleanly.
I like being close enough to the work that I can see what is real.
That is the in-between leader role I keep finding myself in. Not detached strategy. Not fake thought leadership. Not just doing tickets in a vacuum.
I mean standing close enough to the people, tools, systems, and outcomes to see where the translation is failing.
Then fixing it.
That is where I feel most like myself.
The Joy Is Making Necessary Work Actually Work
The joy for me is not in pretending things are simpler than they are.
The joy is taking complex, necessary work and making it work.
It is the iteration. The refining. The annoying second pass. The moment when a system that used to be confusing starts producing clarity. The moment when a team stops guessing. The moment when a builder or operator can finally see what is happening without needing to become a full-time software person.
That is satisfying to me.
I like taking things that are scattered and turning them into an operating rhythm.
I like finding the gap between what people say they want and what the process is actually producing.
I like making the next move obvious.
Sometimes that is not glamorous. A lot of the best work is not glamorous. It is documentation. Triage. Clear handoffs. Better follow-up. Cleaner review. Saying the thing everyone is dancing around. Fixing the detail that keeps causing five downstream problems.
That is fine.
I am not looking for glamorous. I am looking for useful.
I am not looking for glamorous. I am looking for useful.
The Skill Was Earned in the Hard Parts
The skills I trust most are not the ones that look clean on a resume.
They are the ones that came from hard work getting harder.
Technical problems. Political problems. Miscommunication. Mistakes. People hearing different things. Tools breaking. Systems half-working. Expectations getting fuzzy. Someone needing to own the next move when nobody wants to say what went wrong.
That is where I have built a lot of my actual capability.
Relentless follow-through sounds nice until you are the one who has to keep following through after the easy energy is gone.
Proof sounds obvious until you are the one who has to show what happened, what changed, what still needs work, and what the client or team can trust.
Clear communication sounds basic until you are in the middle of a messy project and realize half the damage came from people not saying the true thing early enough.
I do not fake certainty.
If I know, I will say I know.
If I do not know, I will say I do not know yet, then I will go get the answer or the next move.
That distinction matters to me more than it used to.
Need Is Not Abstract
The need piece is where this gets personal.
Clients need clarity.
Family needs presence and follow-through.
Teams need someone who can turn moving parts into a plan.
Fellow engineers and younger builders need examples of people who do not pretend everything is easy, but also do not collapse into excuses.
Contractors need help keeping track of their business and their brand while the day-to-day work keeps moving.
They do not need another dashboard nobody checks.
They do not need another vendor making promises and disappearing behind jargon.
They do not need someone telling them AI will magically fix operations they have not named yet.
They need coordination. Documentation. Triage. Verification. Honest communication. Someone to help them see what is happening before it becomes a mess.
That is part of where the right client work still fits for me.
The right client work is still the craft shop. The place where the work deserves care, context, and standards. The place where we can build something useful and not just sell motion.
The next version of that instinct belongs on the client side.
Human-in-the-loop orchestration. Agent support, but not agent theater. Documentation, triage, verification, coordination, and visibility so contractors are not losing track of the business while trying to run the business.
That is not a random pivot.
It is the same pattern showing up in a clearer form.
The Trades Changed How I See The Work
The plumbing apprenticeship has changed how I think.
You cannot hand-wave field work forever. At some point the fitting is right or it is wrong. The order matters. The prep matters. The mess you create now becomes the thing someone else has to crawl under a house and fix later.
That has a way of sharpening your standards.
It reminded me that complexity has to be broken down into ordered, bite-sized pieces.
You still need speed. You still need execution. You still need efficiency.
But if you skip the beat where you architect the thing correctly, you are not saving time. You are just creating a future mess with better confidence.
That applies to software.
It applies to agency delivery.
It applies to AI agents.
It applies to documentation.
It applies to client communication.
Move fast, sure. But do not move so fast that you make garbage someone else has to clean up.
I have lived enough of that from both sides.
I am not interested in building more of it.
I Am Done Treating Good Values Like A Liability
One of the harder lessons has been realizing how often openness, transparency, accountability, and open-source collaboration get treated like a threat.
Not by everyone.
But enough that you notice.
There are environments where saying the true thing is seen as a problem. Where documenting the work makes people uncomfortable. Where accountability is welcomed in theory and resisted in practice. Where collaboration is fine until it exposes who is actually contributing.
I am done pretending that is normal.
I am done making room for chronic excuses, dishonesty, backstabbing, or dysfunction just because someone knows how to dress it up professionally.
I can be generous. I want to be generous.
But generous does not mean doing serious work for free forever.
Generous does not mean lowering standards until everyone feels comfortable.
Generous does not mean carrying people who do not want to improve or own their work.
Life is too short for that.
The work is too important for that.
Building for the Future Means Choosing Better Now
The future I care about includes AI agents.
It includes upcoming talent.
It includes younger engineers and builders who are going to inherit a weirder, faster, more automated world than the one I came up in.
That means the standards matter more, not less.
If agents can move faster, the values behind the work matter more.
If tools can generate more output, the taste and review process matter more.
If systems can run around the clock, the humans need to be clearer about what deserves attention, what deserves proof, and what should not be automated in the first place.
I want to build for that future.
But I do not want to repeat the old compromises to get there.
No compromise on values.
No compromise on standards.
No compromise on transparency.
No compromise on honest communication.
That does not mean being rigid for the sake of it. It means knowing what cannot be traded away without turning the work into something I do not want to be part of.
Maybe Fulfillment Is Not One Lane
I do not think fulfillment is one perfect job title.
At least not for me.
It is not just agency owner.
It is not just developer.
It is not just trades apprentice.
It is not just AI systems guy.
It is not just writer, operator, strategist, or builder.
It is the pattern underneath all of those things.
Wrangle chaos.
Stay close to the work.
Tell the truth.
Build useful systems.
Help people see what is happening.
Break complexity into something they can actually use.
Keep the standards high.
Give generously, but stop confusing generosity with self-erasure.
That is the work that still feels alive.
That is the work I am trying to choose more deliberately now.
Not because it is easy.
Because it is useful.
Because it uses the skills I actually earned.
Because it still has joy in it.
Because people need it.
And because it is still mine.
Quick Answers
What is the work that still feels alive?
Wrangle chaos. Stay close to the work. Tell the truth. Build useful systems. Help people see what is happening.
How do AI agents fit into this?
If agents can move faster, the values behind the work matter more. If tools can generate more output, the taste and review process matter more.
What did the trades change?
Complexity has to be broken down into ordered, bite-sized pieces. Move fast, sure. But do not move so fast that you make garbage someone else has to clean up.
That is the work that still feels alive.
Source Note
This post was sparked by Jason Cohen’s essay, Finding Fulfillment, especially the Joy + Skill + Need framing. This is not a summary of Cohen’s article. It uses that framework as a starting point for my own reflection on agency work, AI systems, trades, standards, and the kind of work I want to keep choosing.
