SecondBrain
Ask the Brain
Index/Sourceupdated Sat May 09 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Autonomous Software Development with Blitzy (CXOTalk)

enterprise-aiautonomous-codingblitzylegacy-modernizationciovibe-coding

Autonomous Software Development with Blitzy (CXOTalk)

Enrique Ibarra (CIO, GNP — Mexico's largest insurer) on a real ~1,000-developer pilot of Blitzy, an autonomous software development platform. Concrete numbers from production, not a vendor pitch deck.

Key claims

  • Headline numbers:
    • 5–10× engineering velocity across pilot use cases
    • 80–95% of work done autonomously by Blitzy, depending on use case
    • Java 8 → Java 21 migration: ~100% autonomous
    • Angular frontend modernization: ~80% autonomous (the last 20% via IDE co-pilots)
  • Why modernize: 20-year-old MAP/IBM mainframe; cost + future COBOL talent shortage (universities don't teach it).
  • Pilot structure (4 use cases on one real system): backend lang upgrade, frontend upgrade, new feature build from a business-language prompt, security vulnerability remediation.
  • Autonomous platform ≠ co-pilot: no IDE. You write a detailed prompt; the platform's internal agentic architecture autonomously generates the changes. Different paradigm from Vibe Coding.
  • Two-tier tool stack works: Blitzy does the heavy lifting; IDE-based co-pilots polish the last 20%.
  • Encoding governance as input: corporate technical guidelines, security guidelines, test requirements all go in as part of the prompt — not post-hoc review. Same insight as Praveen's "policy .md files" in Agentic AI in the Enterprise (Praveen Akkiraju, CXOTalk).
  • Role shift: developers become editors and orchestrators, not creators. "The human is not writing the code. The human is directing a platform on how to write the code."
  • Change management: skeptics flipped within weeks once they saw results. Engineers became excited about prompt-engineering as a craft.
  • Phased human-in-the-loop playbook for CIOs:
    1. Target high-effort, low-risk friction first (lang upgrades, doc gen, test suite generation, vuln remediation)
    2. Train engineers from creators → editors → orchestrators
    3. Human's role becomes prompt design + architecture review + AI execution validation
  • Strategic payoff beyond cost: ship new insurance products in weeks rather than months; shift IT from maintaining the business to dictating market pace.
  • Rollout horizon: 7 additional teams next; full transformation in ~2 years. Will reduce reliance on external software-factory developers.

Cross-source resonance

  • 5–10× velocity claim sits alongside Karpathy's "well above 10×" for top practitioners (Andrej Karpathy on Agentic Engineering (Sequoia AI Ascent)) and Boris's 100% autonomous code at Anthropic (Boris Cherny on Coding Is Solved (Sequoia AI Ascent)). Three independent sources triangulating order-of-magnitude productivity gains.
  • Role shift to editor/orchestrator echoes Karpathy: "You're in charge of the taste, the engineering, the design… engineers are doing the fill-in-the-blanks."
  • Governance as prompt input = Praveen's policy .md files = Karpathy's spec-first approach. Three sources, same recipe.
  • Bounded use cases first matches Praveen's Bounded vs Unbounded Tasks framework — language upgrades and security remediation are highly bounded.

Critique

  • Single source, single company, vendor-favorable framing — discount accordingly.
  • 80–95% autonomy rate doesn't mean 80–95% time saved; the 20% polish + prompt engineering + review can dominate. Worth probing if more sources land.

Cross-links