Theo’s take lands where I live: vibe coding isn’t a developer replacement; it’s a way to replace chunks of engineering you shouldn’t waste cycles on. For small teams, that’s gold—ship the throwaway glue and UI scaffolding fast, then review the bits that actually matter. Agentic flows are great; vibe coding is fine when you accept the cost: you must still understand the code, and AI won’t save a broken process. Measure output by shipped code, not demos. Keep teams small, wire AI into the workflow, and treat packages and prompts as the same trade-off.