Splitting Until It Fits

Описание и применение

Разделение задач на небольшие, независимые итерации позволяет избежать скрытых зависимостей, упрощает тестирование и параллельную работу.

Задача

Large code changes in a monolith become hard to manage and test when a single task spans many files and dependencies, leading to unclear boundaries and difficulty in parallelizing work.

Результат

By splitting work into small, dependency‑free iterations, tasks become testable, parallelizable, and easier to manage, reducing the risk of hidden dependencies.

Рабочий процесс

• Define a task as a service that takes runtime from the platform.
• Break the task into stages, sub‑stages, and iterations.
• Ensure each iteration is one concern: 1–2 files + its test.
• Check that the executor does not need to look up anything; if they do, split further.
• Order iterations by data dependency; independent iterations can run in parallel.
• Run a package‑specific test for each iteration (e.g., go test ./internal/repository/order/... -race -count=1).
• After all iterations, run a full suite once for formatting, vetting, linting, and race checks.

Доказательства

The executor had to look something up.

Источник

An iteration that can't be checked isn't finished, it's abandoned.

Источник