No CS degree. No bootcamp. Just 10 years on factory floors and a stubborn belief that the software I needed should actually exist.
Here's how AI tools helped me make the jump — and 5 lessons from manufacturing that turned out to be my biggest advantage.
From Factory Floors to the App Store
I spent a decade in manufacturing engineering. Process optimization, quality control, equipment troubleshooting — the kind of work where every minute of downtime costs real money.
The whole time, I had one recurring frustration: the software tools I needed were terrible. Clunky tracking systems. Overpriced dashboards. Apps that felt like they were designed by people who had never touched a production line.
So I tried to learn to code. Multiple times. Tutorials, online courses, side projects. Every attempt hit the same wall — not because I couldn't think logically, but because the jump from "hello world" to a working product felt impossibly wide.
Then AI coding tools changed everything.
Why AI Was the Missing Piece
AI didn't teach me computer science. It did something better — it met me where I was.
Suddenly I could focus on what I was already good at:
- Defining the problem clearly — engineering trained me for this
- Breaking it into components — process engineering is literally this
- Iterating fast — prototype, test, improve, repeat (factory mindset)
AI handled the syntax. I handled the thinking.
Within months, I shipped my first iOS app. Then another. And another.
What I'm Building Right Now
- Pregnancy & Parenting App Suite — My wife and I couldn't find an app that wasn't riddled with ads or missing features. So I built one.
- Enterprise AI Platform — RAG chatbot + auto-generated presentations for enterprise adoption. My manufacturing background directly applies here.
- Markdown Note App — Notes for iOS with iCloud sync and on-device AI. Every note app was either too simple or too complex.
- ADHD-Friendly Task Planner — Eisenhower Matrix meets Pomodoro timer. Built for brains that work differently.
- AI Coding Terminal — Windows-native terminal with multi-agent control. The tool I wish I had when I started.
5 Lessons Manufacturing Taught Me About Software
1. Nobody cares about your architecture.
On the factory floor, nobody cares how elegant your process flow diagram is. They care if the product comes out right. Same with apps — solve the problem, and nobody asks if you used MVVM or MVC.
2. Ship first. Optimize later.
We had a saying: "Don't let perfect be the enemy of good enough for Tuesday's shipment." Get it working, get it in front of users, then iterate.
3. Constraints breed creativity.
Tight budgets. Broken equipment. Real deadlines. Manufacturing forces you to find creative solutions — and that's exactly what indie dev demands when you're the designer, developer, tester, and marketer all at once.
4. Ask "why" five times.
Toyota's "5 Whys" technique is the best debugging framework I've ever used. Don't fix the symptom. Keep digging until you find the root cause.
5. Domain knowledge is your superpower.
No CS grad knows what a manufacturing engineer needs from a monitoring tool. No bootcamp teaches what an expecting parent wants from a pregnancy app at 3 AM. Your non-tech experience isn't a weakness — it's the unfair advantage that helps you build things people actually want.
My Stack
| Category | Tools |
|---|---|
| Mobile | Swift, SwiftUI |
| Web | React, Next.js, Tailwind CSS |
| AI/ML | Python, LangGraph, LLM APIs |
| Infra | Docker, Supabase, Local AI Server |
The Honest Truth
AI didn't make me a software engineer. It made me a software builder.
I still don't know half of what a CS grad knows about algorithms. But I can identify a real problem, design a solution, and ship a product that people use. That's enough to build meaningful things.
If you're sitting on deep domain expertise in a non-tech field — healthcare, education, construction, whatever — the barriers have never been lower. You don't need a degree. You need a problem worth solving and the will to ship.
I'm new to DEV and writing about AI-assisted development from a non-CS perspective. If this resonates, I'd love to hear your story.
What did your "before" look like?
Top comments (0)