The Pivot
Fifteen years in food service teaches you a lot of things: how to work under pressure, how to communicate clearly, how to show up every day even when you don’t want to. It also teaches you that you want something different.
I’d been tech-curious for twenty years — tinkering with Linux, reading about programming, building small things that never went anywhere. But the leap from “curious” to “committed” felt impossibly wide.
Then AI changed the equation.
AI as a Teacher, Not a Crutch
The common narrative is that AI writes code for you. My experience was different: AI was the teacher I never had.
When I hit a wall with Rust’s ownership model, I could ask Claude to explain it five different ways until one clicked. When my NixOS config wouldn’t build, I could paste the error and get a guided diagnosis instead of drowning in documentation.
This wasn’t cheating. This was having a patient, knowledgeable mentor available 24/7. The kind of mentorship that’s usually locked behind a CS degree or a junior dev position.
The Learning Loop
My daily cycle looked like this:
- Read a concept or tutorial
- Build something small with it
- Break it intentionally to understand edge cases
- Ask AI to explain what I didn’t understand
- Repeat
The key insight: I wasn’t learning from AI. I was learning with AI. The building was mine. The understanding was mine. AI just removed the friction of getting unstuck.
Why Rust
People ask why I chose Rust as one of my primary languages. The honest answer: because it forces you to understand what you’re doing.
Rust doesn’t let you hand-wave memory management. It doesn’t let you ignore error handling. Every decision is explicit. Coming from food service — where “close enough” can mean a health code violation — I appreciated a language that valued precision.
My first real Rust project was Astral Key, a Web3 authentication microservice. Building it taught me more about systems programming than any tutorial could. The compiler errors are the curriculum.
What Food Service Actually Taught Me
Here’s the thing nobody tells you about career changes: your previous experience isn’t wasted. It’s transferable.
| Food Service Skill | Developer Equivalent |
|---|---|
| Working the line during rush | Handling incidents under pressure |
| Managing inventory | Resource planning and optimization |
| Training new staff | Mentoring and documentation |
| Dealing with difficult customers | Stakeholder communication |
| Opening/closing procedures | CI/CD pipelines and deployment checklists |
| Menu development | Product planning and iteration |
The work ethic is the same. The problem-solving is the same. The teamwork is the same. The domain changed; the skills didn’t.
The Projects That Made It Real
I learn by building. Here’s what I shipped during the transition:
- This portfolio — Astro, GSAP, deployed on GitHub Pages. Taught me frontend fundamentals and static site generation.
- Frostbite Gazette — AI-curated news aggregator on Cloudflare Workers. Taught me API integration and edge computing.
- Astral Key — Rust microservice with Axum and SQLx. Taught me systems programming and async Rust.
- NixOS Cluster — 4-host deployment with Colmena. Taught me infrastructure as code and declarative systems.
Each project was chosen to stretch me in a different direction. Each one failed spectacularly at first. Each one eventually worked.
What I’d Tell Someone Starting This Journey
- Build real things. Tutorials give you knowledge. Projects give you understanding. Ship early, ship ugly, iterate.
- Use AI as a pair programmer, not an autocompleter. The value isn’t in the code it writes — it’s in the explanations it gives.
- Your background is an asset. Every industry has unique problems that need solving. Your domain knowledge + technical skills is the combination.
- Embrace the uncomfortable. If you’re not confused, you’re not learning. Rust’s borrow checker making you miserable means it’s working.
- Be public about your learning. Write about what you’re building. Share your mistakes. The community is more supportive than you expect.
Where I Am Now
I’m not done learning. I never will be. But I’ve gone from “tinkerer” to “someone who ships production applications.” My NixOS cluster runs real workloads. My Rust code handles real authentication. My infrastructure runs real services.
Fifteen years in food service gave me the discipline. AI-assisted learning gave me the velocity. The building gave me the skills.
If you’re thinking about making a similar transition — whether you’re in food service, retail, or any other field — the tools have never been more accessible. The question isn’t whether you can. It’s whether you will.