---
title: "Dan Shapiro: You Don't Write the Code. You Don't Read the Code Either."
slug: dan-shapiro-you-dont-write-code-2026-02-13
type: source
created: 2026-06-17
updated: 2026-06-17
status: active
tags:
  - source
  - dark-factory
  - strongdm
  - validation
sources:
  - https://www.danshapiro.com/blog/2026/02/you-dont-write-the-code/
related:
  - dark-factory
  - software-factory
  - digital-twin-universe
  - cxdb
  - healer
confidence: high
contradictions:
  - The article argues humans must stop reading generated code, while also foregrounding security and quality problems that require stronger validation systems.
bead_refs:
  - dark-factory-rr4
---

# Dan Shapiro: You Don't Write the Code. You Don't Read the Code Either.

Source URL: [Dan Shapiro blog](https://www.danshapiro.com/blog/2026/02/you-dont-write-the-code/)

Published: 2026-02-13. Captured: 2026-06-17. Provenance: primary article by Dan Shapiro about StrongDM's dark factory work.

## Compact Takeaways

- The core operating shift is: the AI writes code, and reviewing every pull request becomes the bottleneck.
- The new engineering job is to solve the problems created by not writing or reading code: quality, understanding, observability, and validation.
- StrongDM used a local digital twin of enterprise SaaS systems so generated products could be tested against realistic external behavior.
- The article names two internal systems: [[cxdb]], an observability layer, and [[healer]], a diagnostic and repair loop built on top of that observability.
- The most reusable practice is asking why a human is doing a manual validation step, then turning the answer into a validation rule.

## Wiki Implications

- [[dark-factory]] should be treated as an operating model, not just an AI coding style.
- [[code-review-vs-validation]] is the central tradeoff: if humans stop reading code, validation systems must become first-class engineering work.
- [[digital-twin-universe]] is evidence that high-fidelity test environments become more important as code review becomes less central.

## Caveats

- This source is narrative and observational. It reports specific StrongDM practices but does not provide formal specifications or implementation details.
- It presents an aspirational lights-off model, but the examples still imply human judgment at the level of factory design, bootcamps, validation policy, and tool building.