The SaaS Model Is Breaking, and AI Agents Are the Reason

Vibe Coding Is Dead: The Rise of Agentic Engineering

THE THREE-PANEL FRAMEWORK Panel 1: Vibe Coding * You → Prompt → Model → Code * Fast to start * Feeling over structure * Good for prototypes * "You ask the model to solve the problem directly" Panel 2: What Changed * Stronger models are not the whole answer * The new bottleneck is context, rules, and review * Engineer writes spec → Sets rules → Lets agents work → Reviews output * "You code less. You steer the system more." Panel 3: Agentic Engineering * Agents build. The human orchestrates. * Bring together: spec, goal, constraints, history, data, rules, tools, tests * "More scalable. More repeatable. Better results." KEY QUOTES > "Many people have tried to come up with a better name for this to differentiate it from vibe coding. Personally, my current favorite is 'agentic engineering.'" — Andrej Karpathy > "The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software." — Andrej Karpathy > "I think by the end of the year, everyone is going to be a product manager, and everyone codes. The title software engineer is going to start to go away." — Boris Cherny > "You can outsource your thinking but you can't outsource your understanding." — Tweet Karpathy thinks about every other day ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Claude Code at the Organization Layer: What Actually Changes

WHAT ACTUALLY CHANGES WHEN CLAUDE CODE REACHES THE WHOLE ENGINEERING ORGANIZATION METRICS THAT ACTUALLY MATTER Stop measuring: * Lines of code per developer * Token consumption * Individual productivity Start measuring: * Cycle time (Claude-assisted vs non-assisted PRs) * Time to first PR for new hires * PR throughput with quality counterweight (defect rate, rollback frequency) * Incident resolution time * Maintenance burden trajectory NON-ENGINEERS BUILDING SOFTWARE Examples from one company: * Support team: Tool surfacing relevant past tickets and customer history * Finance team: Expense categorization assistant * HR team: Onboarding checklist app pulling from live systems What engineering built: * Architecture patterns for internal apps * Plugin marketplace with pre-approved skills/MCP connections * Managed permissions (read from X, write to Y, not Z) * Audit logs for AI-generated changes The shift: Engineering didn't build the apps. Engineering built the conditions under which apps could be built safely. ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

The SaaS Model Is Breaking, and AI Agents Are the Reason

So, quick context before we dive in. A couple of weeks ago I published a piece on my blog about how AI agents are quietly breaking the SaaS pricing model. And honestly? I didn't expect what happened next. The post just… took off. My inbox has been wild. CFOs, founders, a few VCs, even a couple of procurement leads who I'm pretty sure have never emailed anyone voluntarily in their lives. All asking the same kinds of questions. ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Gemma 4: Google's Open-Source LLM Competing with Chinese Models

WHY APACHE 2.0 MATTERS Previous Gemma licensing: * Custom "Gemma Terms of Use" * Usage-policy provisions * Constraints on commercial deployment Apache 2.0: * Fine-tune for commercial use ✓ * Redistribute fine-tuned variants ✓ * Embed in commercial products ✓ * No ongoing license obligations ✓ ON-DEVICE AI IMPLICATIONS What's new: * Full conversational AI on phones, offline * No data leaving device * No API costs * No connectivity requirements Use cases: * Healthcare apps (privacy) * Education (offline areas) * Finance (data sovereignty) * Any privacy-sensitive application DATA SOVEREIGNTY The shift: * European regulators increasingly uncomfortable with US-hosted APIs * GDPR requires either locked regions or self-hosted * Gemma 4 + Apache 2.0 = viable self-hosted option * Regulated industries now unblocked CHINESE MODEL GOVERNANCE QUESTIONS For Western organizations considering Chinese open models: 1. Training data provenance — Can you verify? 2. Embedded refusals/biases — Different content policies 3. Export-control compliance — Check with legal 4. Strategic precedent — Building on competitor infrastructure Not disqualifying, but requires conscious decision ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Musk vs. Altman: The OpenAI Legal Battle Explained

FOR TECH LEADERS 1. Corporate structure creates 5-10 year litigation exposure 2. Nonprofit pivots require AG negotiation, not just board approval 3. Mission-aligned structures (PBC) gain credibility advantage 4. Document founder discussions formally 5. Co-founder departure terms matter more than ever FOR INVESTORS 1. Governance risk is now diligence requirement 2. Demand mission-protection documentation 3. Monitor AG agreements and state oversight 4. Understand partner-investor risk compounding WHAT TRIAL REVEALED > "The picture that emerged is not one of villains stealing a charity, nor one of crusaders defending a mission. It is one of co-founders making consequential decisions under significant uncertainty, with informal arrangements that proved inadequate to the scale of value the technology eventually created." KEY QUOTE > "Musk will likely lose the case but is succeeding at something his lawsuit may not have intended — establishing a public record of how AI labs are actually governed, and creating durable pressure for that governance to become more formal, more transparent, and more constrained." ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.