Field notes on leadership, engineering, and decision-making under pressure.
A 16-year-old asked for a record player for Christmas. When he opened that album and saw the artwork, the lyrics, the photos — he was blown away. He didn't know that stuff existed. And it reminded me of exactly what's happening with AI right now.
I've watched it happen more times than I can count. A guy builds something. Works his ass off. The business takes off. And somewhere along the way, he looks at the woman who was there through all of it and doesn't feel connected to her anymore. They didn't grow apart because they fell out of love. They grew apart because they grew alone.
Early in my business, I said yes to everything. Every client. Every project. Every opportunity that came through the door. I had no filter. I didn't have a clear goal, so I couldn't evaluate whether something was moving me forward or just keeping me busy.
The world doesn't stop for anyone. You're in a current. Always have been. The question is what you're doing inside of it. Most people are floating. At some point the floating turns into digging. And one day you look up and realize you're standing at the bottom of a hole you dug yourself.
I filed for bankruptcy at 25. Lost my car. Rode a bike 15 miles to wait tables because I had no other option. I didn't have a plan. I didn't have a mentor. I just knew that what I was doing wasn't working and something had to change.
I built a seven-figure company chasing money. On paper it was a success. In reality I was chasing a carrot that was never going to feed me. The money came, but peace didn't. Fulfillment didn't. Presence didn't. I was making more than I ever had and I'd never been more empty.
I paid $20,000 for a program that their own team later told me doesn't work for my audience. That's the pattern — someone builds a system that worked for them, packages it up, and sells it like it's universal. The cost of getting this wrong isn't just the invoice.
Every problem you're stuck on right now is sitting in a box you put it in. You didn't do it on purpose. Something feels too big, too complicated — so you define it. Label it. Shove it on a shelf. The problem is, once it's in the box, you can only see it from the inside.
For two years, I believed I couldn't make more than $500 a week. Not because the market wouldn't support it. Not because I didn't have the skills. I had an invisible ceiling I didn't know was there — and every decision I made ran through a filter that said: this is as good as it gets for someone like you.
We got married with no money. I don't mean we were tight. I mean we were in $60,000 of debt and not even making $60,000 a year. There was no runway. No savings account. No 'once we're in a better position.' We just looked at each other and said — let's do it.
At some point, you figured out who you're supposed to be. And instead of stepping into it, you did what most of us do. You whispered it. You buried it. You put it in a box with glass walls — where you can see the life you want but nobody on the outside can hear you screaming for it.
Some mornings I wake up and I'm ready. Others, I'm a lawnmower engine that won't turn over. After enough of those mornings, your brain starts running on autopilot. Scattered thoughts. Half-finished ideas. Reactions instead of intentions. And all of that is energy going somewhere.
Eighty thousand dollars in late invoices. My wife saw the pattern. I dismissed her. This is what I learned about the difference between making a decision and owning it.
I told a client they were 'one hurricane away' from losing 50 years of data, and the budget was approved instantly. Here is why your technical case is failing and how to translate it into language leadership can actually fund.
Your AI pilots aren't failing because of the technology; they're failing because of a translation layer breakdown. Here is why you can't demo your way into production, and why skipping the 'compression protocol' stalls deployment.
Premature commitments aren't optimism. They're performance. Here is why saying 'yes' too fast destroys your authority and how to shift the burden of urgency back where it belongs.
Speed increases when inputs are unfiltered, but progress happens when the system enforces clarity. Here is why your team is burning out on 'waste heat' and how to shift the burden of clarity back to the requester.
I tried not to micromanage, but I created dependency instead. Here is how 'being the system' destroys your authority and why you must let systems fail to actually lead.
We lost a major account because design and development worked in silos. Here is why polished work often misses the mark and the structural change required to fix the workflow.
I lost my COO, my developer, and a client in one phone call while dealing with family tragedy. Here is why it wasn't betrayal, but abdication—and why firefighting is actually just tolerated volatility.