AI for Software Engineering

Code models, repository context, patch generation, test-driven agents and SWE benchmarks.

12concepts
101flashcards
87minutes of reading
  1. 01 AI-Assisted Code and Maintainability Signals The measured side effects of assistant-heavy development, covering duplication, the collapse of refactoring signals, rising complexity and delivery instability, and which of these signals are strong enough to act on. advanced 8m 6 cards
  2. 02 Code Generation Benchmarks and pass@k How HumanEval turned code evaluation into execution, why the unbiased pass@k estimator exists and how it is derived, and why saturation and contamination pushed the field toward time-stamped benchmarks. advanced 7m 7 cards
  3. 03 Code Review by Model Why review is a better fit for current models than authoring, the precision problem that determines whether it is used, and the classes of finding worth reporting. advanced 7m 12 cards
  4. 04 Fill-in-the-Middle and Completion Models Why a left-to-right model cannot do the most common editing task, the training transformation that fixes it, and the latency budget that shapes everything about inline completion. advanced 7m 10 cards
  5. 05 LLM-Assisted Code Migration at Scale The best-documented industrial win for code models is not feature development but mechanical migration, where change location is searchable, correctness is machine-checkable, and the work was previously too tedious to fund. advanced 8m 5 cards
  6. 06 Repository Context and the Retrieval Problem Why a model with a large context window still cannot see a codebase, what makes code retrieval different from document retrieval, and the signals that actually locate relevant code. advanced 7m 12 cards
  7. 07 Reviewing Machine-Authored Changes When generation gets cheap, human review becomes the binding constraint on delivery, and the queue behaves the way queues do: larger diffs, longer waits, and a reviewer whose attention is the scarce resource. advanced 7m 6 cards
  8. 08 SWE-bench and Agentic Coding Evaluation What resolving a real GitHub issue measures that a function-completion benchmark does not, the contamination and scoping problems that complicate it, and how to read a reported score. advanced 7m 12 cards
  9. 09 Test-Driven Agents and Verification Loops Why an executable check transforms an agent's reliability, how to structure the loop so it converges, and the failure where the agent optimises the test rather than the code. advanced 7m 12 cards