// BLOG
Writing
Essays and field notes on Symfony, open source, and AI tooling, and how software engineering changes when agents join the process.
// OPINION
Kill the MCP →
I deleted the MCP server from a Mate prototype and kept the tools. What that cost, what it bought, and why the reflex is the thing worth killing.
// OPINION
Vibe coding is no-code without a custodian →
Vibe coding can produce maintainable software. The harder question is who owns its dependencies, decisions and failures after launch.
// OPINION
The wrong debate: what PHP taught me about agentic software →
MCP or CLI is the wrong fight. What PHP with Composer, PSR and Symfony already learned about building things together, one layer down.
// SKILLS
The last mile: distributing Agent Skills to real agents →
The polyfill that bridges where the Agent Skills standard is heading and what agents can read today, and why distribution, not the protocol, was the real problem.
// MCP
Skills over MCP: shipping Symfony know-how with Mate →
What an Agent Skill actually is, how you serve one over MCP, and lessons from building a reference implementation against a spec that kept moving.
// ESSAY
What happens to innovation when implementation becomes almost free? →
When code, design and content all get cheaper, maybe implementation was never the bottleneck. A note from the classroom on friction, the statistical mean, and where excellence shows up.
// AI
Giving AI assistants eyes →
Highlights from the Symfony Mate Q&A: the dev-only MCP server that lets AI assistants look inside your running app, and why better context beats more context.
// OPINION
Why six people are enough and what coding agents have to do with it →
Six developers run Sulu, its enterprise projects and its cloud services. That only works because of ownership and context, and those are exactly what coding agents need too.
topics: ai innovation maintenance mate mcp opinion ownership php skills sulu symfony teaching teams vibe-coding
Looking for older posts? Browse the archive from asapo.at →