Who Made This Decision?
We built in two months a product that would have taken a year. When we reviewed it, a small change touched 80 files. The AI didn't write bad code: it made design decisions nobody reviewed.
We built in two months a product that would have taken a year. When we reviewed it, a small change touched 80 files. The AI didn't write bad code: it made design decisions nobody reviewed.
A code review of a SaaS app a non-technical colleague vibe coded in 5 days. God tables, missing auth, dual systems, and the meta-lesson about AI-compressed timelines.
A security review of millionco/expect — a Claude Code plugin that runs AI-driven browser tests via Playwright. The skill is safe. The CLI decrypts every cookie in your browser.
The skills ecosystem is growing fast. A recent study found malicious payloads in 13% of published skills. Here's what that looks like in practice and what you can do about it.
Your AI coding agent installs packages to solve problems. It doesn't check if those packages are GPL, unlicensed, or pulled from a sketchy mirror. Here's how to protect your project.
Vibe coding works great solo as is. But what happens when your team grows exponentially?
We hand AI our data, our decisions and a good part of our judgment, almost without thinking. We ask Bitcoin for explanations we ask of almost nothing else. I don't think it's about what each technology is. I think it's about what each one asks of us.
For the first time in my career, I feel like this craft is in danger. And at the same time, every day working with agents tells me it isn't. An attempt to hold both thoughts at once.
Wrote about the licensing blind spot in vibe coding — AI agents install GPL, unlicensed, and WASM packages without checking. Includes a zero-dependency audit recipe and a Claude Code skill.
Read the full post → https://augustochirico.dev/blog/vibe-coding-licensing-blind-spot