▸ Blog series
From Vibe Coding to Agentic Engineering
How AI-assisted development grows up — from conversational vibes, to MCP-driven agentic loops, to the review and verification gates that let it ship to production.
- 01
Vibe coding: why projects need more than just logic
Taste, intent, and feel are the new senior-engineer superpowers in the Cursor and Claude era — and how to keep the codebase from becoming a ball of mud.
AI · 8 min read - 02
AI vs traditional development: which fits?
AI vs traditional development: when AI-assisted speed pays off, when traditional engineering is non-negotiable, and the hybrid workflow I favor.
Architecture · 8 min read - 03
Vibe coding: the shift to agentic workflows
MCP, agentic loops, and intent-based engineering. How vibe coding becomes a real architecture pattern, plus the Laravel and MCP stack I run today.
Architecture · 6 min read - 04
Vibe coding vs agentic engineering: which ships?
Vibe coding is for prototypes, agentic engineering is for production. The daily split I use to ship AI-written code without hidden technical debt.
AI · 8 min read - 05
Claude MCP: connecting my dev tools to LLMs
The Model Context Protocol is a USB-C port for LLMs: one MCP server, any host, no MxN integration tax. The architecture, the servers I run, and why it is safe.
AI · 9 min read - 06
AI coding is like an addiction (in the best way)
A level-by-level map of the AI coding workflow: gateway prompts, codebase RAG, then multi-agent orchestration over MCP — and why manual coding now drags.
AI · 8 min read - 07
Stop reading every line of AI-generated code
Line-by-line review breaks on agent-sized diffs. How I moved to specs, property tests, and a multi-agent review pipeline — and the 3% I still read.
AI · 9 min read - 08
Trust is not a QA strategy: test AI code too
AI code is 95% syntactically clean and fails security tests 45% of the time. Half of agentic PRs ship no tests. The verification pipeline I run instead.
AI · 10 min read