Code is clay now

Code has become malleable: agentic coding collapsed the cost of change so deeply that modifying software now feels more like shaping clay than chiseling stone. That enables a modeling workflow where developers slap down rough, working structures, iterate rapidly, and then refine from big shapes to mid-level features to fine details. This fractal modeling works at any layer - solo creators can sketch core product flows in a day, teams can pivot a feature in a couple of days - and watching the real thing in action outperforms planning and mockups. The lower cost of change doesn’t remove the need for judgment: taste, context, guardrails and architecture remain the armature and kiln that prevent rapid edits from collapsing into a messy puddle.

Two practical patterns emerge: artisans and factories. Artisans stay tightly in the loop, leveraging minute-to-minute feedback to design, implement, and polish features (for example, adding a quick “calc block” to a Markdown editor in under an hour), and they judge both UX and code shape as they iterate. Factories push human judgment upstream into pipelines of specs, generators and verifiers that work best on well-structured codebases and repeatable molds - ideal for routine CRUD endpoints or batch bug fixes. Real workflows will blend both: use artisan methods for novelty and feel, factory methods for scale and repetition, and choose the approach that fits the problem.