A Sabbatical With Intent: Rebuilding My Technical Foundations One Step at a Time

After sharing my story in When Plan A Fails, I got a question that’s been rattling around in my head: “What does a sabbatical with intent actually look like?” Fair question. It’s not just endless coffee and philosophical pondering (though there’s been some of that). It’s about deliberately rebuilding what got buried under years of moving fast.

From Recovery to Rebuilding

The first weeks were pure recovery—less code, more sleep, a lot of walks, and permission to not have all the answers. But recovery alone isn’t a plan. Once the fog lifted, I realized I had a rare opportunity: to learn without the pressure of sprint deadlines, to build something slowly and properly, and to rediscover what made me fall in love with this craft in the first place.

So I made a choice. Instead of jumping straight back into job applications or rushing through tutorials, I’d give myself space to go deep. Not just watch courses or read books, but actually build something real—from requirements to deployment—and document every step along the way.

What Intent Looks Like in Practice

Here’s what that looks like in practice: I’m working on a demo backend system—not a toy project, but something that tackles real problems like authentication, data persistence, API design, and deployment. I’m working a focused 40-hour week—treating this demo system with the same discipline and drive I’d bring to any real-world project. I’m documenting everything—the wins, the failures, the “why did I think that would work?” moments—because transparency matters, and because others might find it useful.

But it’s not just about the code. I’m also learning to think differently. Instead of “how fast can I ship this?”, I’m asking “what’s the right way to build this?” Instead of copying patterns I don’t understand, I’m taking time to understand the fundamentals. It’s slower, messier, and honestly more satisfying than anything I’ve built in years.

I’m also giving myself permission to explore. Some days, that means diving deep into distributed systems. Other days, it’s tinkering with DevOps tools, or thinking about how AI can make engineering work more interesting (without replacing the craft itself). The goal isn’t to master everything—it’s to stay curious and build a foundation I can rely on for years to come.

If you’re feeling burned out, stuck, or just curious about what happens when you step off the treadmill, stick around. I’ll be sharing what I’m learning, the mistakes I’m making, and why sometimes the best way forward is to slow down, breathe, and build with intent.