Good Engineering Doesn’t Trust Engineers
Factory workers tell the author they don't trust software engineers, because clean models miss dusty sensors, part batch changes, and cold-morning valve stickiness. Good engineering agrees: NASA, aviation, and nuclear plants build processes around the assumption that engineers can be wrong. AI makes code cheap, exposing that mainstream software development treats code as source of truth, requirements as Jira tickets, and safety arguments as PR comments. The post argues that engineering means making intent explicit and attaching evidence to obligations, separating verification from validation, and applying rigor proportional to risk. It cites NASA's SWEHB, MC/DC coverage, and FRET project, then introduces ReqProof as an agent-driven lifecycle where obligations stay visible and evidence stays attached. The core ideas stand even if you never use the product.