---
id: "prereq-software-engineering-paradigms"
type: "prereq"
source_timestamps: ["00:06:48", "00:10:15"]
tags: ["software-engineering", "methodology"]
related: ["concept-non-technical-engineering", "framework-agentic-eval-loop"]
reason: "Necessary to understand how non-technical work will transform to mimic engineering workflows."
sources: ["s35-compounding-gap"]
sourceVaultSlug: "s35-compounding-gap"
originDay: 35
---
# Familiarity with Software Engineering Paradigms

## Prerequisite: Software Engineering Paradigms

### What you need to know
The speaker uses these terms assuming the audience understands them:

- **Eval loops** — automated evaluation cycles against measurable criteria
- **Linting** — automated code-style and correctness checking
- **Specification roles** — humans who write requirements rather than implement them
- **Red team passes** — adversarial review meant to surface failure modes
- **Evaluation harnesses** — test suites that run automatically against changing artifacts

### Why this prerequisite matters
These are the vocabulary Jones imports into knowledge work via [[concept-non-technical-engineering]] and the [[framework-agentic-eval-loop]]. Without them, the prediction that marketing or legal work becomes "engineering" sounds metaphorical. With them, it sounds operational.