Subscribe to get full access to the newsletter and publication archives.
About
I’m Cengiz Han, and I’ve spent more than two decades building software—from monolithic applications to distributed systems, microservices architectures, and event-driven platforms at scale. Currently, I’m focused on something that’s reshaping how we build software: AI-native development.
This blog is where I explore the complicated, fascinating intersection of AI and software engineering. Not the demos or the hype—the real stuff. The production-ready software development. The workflow changes. The moments where AI genuinely helps, and the places where it spectacularly fails.
What I’m Building
Right now, I’m building fabriqa.ai—bringing these AI-native development principles into practice. It’s one thing to write about spec-driven development and context engineering. It’s another thing to build products with them. Hopefully, fabriqa is where theory meets reality, and I share those lessons here.
What This Is About
We’re in the middle of a fundamental shift in how software gets built. AI coding assistants aren’t just productivity tools—they’re forcing us to rethink entire development lifecycles. How do we maintain quality when AI writes half the code? What does “code review” mean when nobody fully understands what the AI generated? When does rapid prototyping become reckless vibe-coding?
These aren’t theoretical questions. Teams are shipping AI-generated code to production right now, learning the hard way what works and what creates technical debt bombs.
I write about:
AI-native development workflows that actually ship to production
Spec-driven development as the antidote to vibe-coding chaos
Context engineering beyond simple prompt tricks
Production engineering reality with AI in the loop
Team transformation as development practices evolve
Event-driven architectures, microservices, and distributed systems (my first loves)
Who This Is For
You’re a developer, team lead, or engineering leader who knows AI changes the game, but you’re not sure how to play it yet. You’ve seen the demos. Maybe you’ve tried Copilot or Cursor. You’re excited about the potential but skeptical of the hype.
You want to understand how to actually use these tools without creating a maintainability nightmare six months from now. You care about craft, about quality, about systems that work when they’re under load and customers are upset.
If you’re looking for “5 amazing prompts to 10x your productivity,” this isn’t that. If you want to understand how AI-native development really works—where it helps, where it hurts, and how to navigate the transition—you’re in the right place.
My Perspective
I’m a practitioner who’s seen both the promise and the pain. Twenty-plus years means I’ve lived through enough technology waves to know the difference between genuine transformation and repackaged hype. I’ve worked with microservices before they were cool and event-driven systems when they were still hard. I’ve built observability pipelines, scaled distributed platforms, and led teams through technology transitions.
Now I’m learning this AI-native world the same way you are—by building things, breaking things, and figuring out what actually works. I read the research, test the frameworks, talk to teams in the trenches, and try to make sense of it all.
I don’t have all the answers. But I’ve got perspective, experience, and a healthy dose of skepticism. And I believe we’re better off figuring this out together.
Connect
Find me on:
GitHub: github.com/hancengiz
Twitter/X: @hancengiz
LinkedIn: linkedin.com/in/cengizhan
Chat on Substack: https://www.cengizhan.com/chat
Or just read along. Drop me a comment if something resonates or if you’ve got a different take. This stuff is evolving fast, and nobody’s got it all figured out yet. Let’s learn together.
