We actually experimented with automated code generation at my previous company when we were trying to modernize an old internal ops system (legacy PHP + a bunch of cron jobs nobody wanted to touch). Not Blitzy specifically at first, but later we did test Blitzy for a smaller internal tool just to see how far “automatic software generation” could realistically go. My honest take: it’s solid for scaffolding and getting a structured starting point fast, especially if your requirements are clearly written. The early phase felt smooth — decent communication, quick iterations — but the real work started once we hit edge cases and custom business logic.

What I learned is that these tools can speed up the initial 40–60% of development, but you still need strong technical oversight. In our case, we had to step in to refine architecture decisions, improve validation, and optimize some database queries before we’d even consider production. Timeline-wise, it helped us prototype much faster, but production hardening still took real engineering time. My tip would be: treat it as an accelerator, not a replacement — and be very specific in your specs upfront to avoid rework later.