Alex Lieberman introduces the concept of the Software Factory, an engineering paradigm where building software shifts from individual craft to an industrialized production line. Rather than humans writing every line of code, agents handle writing, reviewing, testing, and deploying software while humans design the system and set guardrails. He cites examples like StrongDM (where code must not be written or reviewed by humans), Ryan Carson's "Code Factory" (shipping over a thousand pull requests via agents), and major companies like Anthropic (90%+ AI-written code) and Google (75% AI-generated code) as proof points.
The article presents a Software Factory Ladder with five levels (0–4), ranging from fully manual "Artisan" work to an "Autonomous Factory" where agents catch bugs, fix them, and ship changes before any human is aware. Lieberman provides diagnostic questions to help leaders assess where their engineering org sits on this ladder and practical guidance for climbing each rung — from simply giving engineers AI tools (Level 0→1) to eliminating the human review bottleneck (Level 2→3) by defining "low-risk" criteria and letting agent-reviewed, test-passing changes auto-merge.
Beyond engineering, Lieberman argues that verifiability is the key criterion determining which business function becomes the next "factory." Functions with automatically checkable outputs, digital workflows, high volume, and reversible mistakes — such as QA, data pipelines, DevOps, and parts of finance — are most ready for industrialization. Strategy, design taste, and relationship-building remain least factory-ready due to their subjective nature. He emphasizes that the real metric isn't "percentage of code written by AI" but how much of the production line runs without a human in it.
A Reddit discussion in r/EngineeringManagers explores how small engineering teams are practically using AI tools beyond the hype cycle. The original poster manages a small team working on a mature, monolith-adjacent platform and has adopted GitHub Copilot (agent mode, chat, PR reviews) but is struggling to achieve the promised efficiency gains while balancing ongoing maintenance and feature development. They specifically call out the lack of recognition around the learning curve and upfront investment required for meaningful AI integration.
The most upvoted response argues that AI code generation is overrated while AI as a research, brainstorming, and debugging partner is severely underrated. One commenter on a greenfield project reports their team of 3 achieves the output of a pre-AI team of 6, primarily by reducing coordination overhead — each developer gets an AI partner to bounce ideas off. The tool of choice for that team is Claude Code used in agent mode.
Another highly insightful comment outlines an iterative journey: using AI to generate characterization tests, then adding code coverage checks, mutation testing, linters, and documentation — essentially building all the engineering discipline that should have existed for humans — before AI starts producing reasonable code. The consensus is that AI delivers real value only when proper guardrails (testing, linting, documentation, code review) are already in place, and that the transition requires genuine upfront investment that the hype tends to gloss over.