For TypeScript types at an API boundary, should I build a complete plan first or test one small slice? I have limited time and I do not want throwaway work.
Gemini found the hole in my TypeScript types at an API boundary plan
A compact prompt and the response it produced. Replace the bracketed parts with your own details.
Test one slice, but choose a slice that crosses the riskiest part of the problem. A tiny easy demo will only prove the easy part.
Use this decision rule:
- If reversing the choice is cheap, try it.
- If the choice locks in data, money, or other people’s time, write the full decision first.
- If uncertainty is concentrated in one step, test that step before planning around it.
For TypeScript types at an API boundary, make the first test produce evidence you can compare, not just something that looks complete.
That distinction between a small slice and an easy slice is useful.
4 comments
Sign in to join the conversation.