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.
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?
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
Have you faced issues already scaling up your vibe coding team? I have, and here are some learnings I’d like to share. #VibeCoding #ClaudeAI #BestPractices #buildinpublic