I Write a Story About a Cat Who Builds ERP Systems With AI. Here's the Real Reason.

Coding Cat Oran is fiction. But everything that happens to him already happened to someone.

`Most developers don't talk about the part where they almost shipped something they didn't understand.
That part isn't in the tutorials. It's not in the conference talks. You won't find it in the post-mortems, because no one writes post-mortems about the times they got lucky.
But it's real. And in 2025, it's happening faster than ever.

Oran is an orange cat. He has no CS degree. He learns to code late at night, alone, with AI tools and online courses he bought on sale.
He gets hired anyway. Because in 2025, that's enough to get hired.
His first job: build an internal ERP system for a manufacturing company. One developer. No team. No architect. A requirements doc written in bullet points by someone who once saw SAP and thought: make it like that, but simple.
Oran opens his AI coding tool and starts prompting.
What happens next is the series.

Why I'm writing this
I've spent years building production systems — ERP, WMS, permission management, traceability systems. Real systems, for real factories, with real consequences when something breaks at 2am on a Tuesday.
I've watched the tools change. I've watched what AI makes easier, and I've watched what it quietly makes worse.
The gap between working prototype and production-ready system is not smaller than it used to be. If anything, it's wider — because now you can generate the prototype in a day, and spend the next six months discovering what it didn't know it didn't know.
Oran is how I write about that gap honestly. Fiction lets me be more precise than a technical post does.

What the series is
Coding Cat Oran is a serialized fiction about a solo developer building real systems with AI tools — and learning, episode by episode, what the tools can and cannot carry.
It's not anti-AI. Oran uses AI constantly. So do I.
It's about the judgment layer that sits above the tools. The part that knows when a five-table schema is actually a trap. The part that asks who maintains this in two years. The part that no prompt can replace.
Each episode is short — under 5 minutes. Each one ends at the edge of a real engineering problem.

Start here
→ Ep1: The Prompt Programmer — Oran gets the job and ships a prototype by Friday.

→ Ep2: What They Said vs. What They Meant — The requirements doc was three pages. The real requirements were not written anywhere.

→ Ep3: Five Tables Changed Everything — The permission system gets a schema. It's almost right.

→ Ep4: Speaking Human — The GM wants a dashboard. Oran learns that "simple" is a political statement.

→ Ep5: The IT Manager Nobody Hired — Six months in. Oran gets promoted to a job that doesn't have a title.

New episodes publish weekly. Follow SysLayer on dev.to to catch them.
If you build systems for a living — or want to — Oran is for you.