Review an API design before you build it
Restricting to 'expensive to change after launch' filters out the style opinions that make API reviews exhausting and produce no change.
Restricting to 'expensive to change after launch' filters out the style opinions that make API reviews exhausting and produce no change.
The 'say so and stop' escape hatch catches the cases where migration is impossible incrementally — which is exactly when a confident plan is most dangerous.
Writing tests from the implementation reproduces the implementation's blind spots. Deriving them from the spec is the only way to catch the requirement that was never…
Scoping to security prevents the model from padding with general advice, which is the usual failure mode of 'review this for security'.