Create a concrete commitment to isolate one pure calculation from effectful shell code.
Isolate one pure calculation from a real mixed IO function in your current codebase Use a function that currently mixes at least one business rule with a clock read, database/API call, random ID, logging side effect, shared mutation, or UI callback. Functional boundary commitment Function I will improve: [name] Current hidden inputs or effects: [clock/API/database/global/mutation/logging] Pure core signature I want: [functionName(inputA, inputB, asOf) -> ResultValue] Shell responsibilities that stay outside: [fetch/persist/retry/log/publish] Fixture I will capture: [one real input case] Proof I will have in three days: [test name, PR link, or before/after diff] Did you create the pure signature and…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in