Be blunt about my plan for TypeScript types at an API boundary. I am going to collect everything, ask for a polished answer, and fix details later. What is likely to go wrong?
How I ask for help with TypeScript types at an API boundary
The useful bit was asking for trade-offs and a smallest test before committing to a full plan.
Three things.
- “Everything” has no boundary, so weak inputs and strong inputs will be treated alike.
- A polished answer can hide missing evidence. Ask for gaps and assumptions before prose.
- “Fix details later” means there is no acceptance test now.
A safer sequence is: define the decision, choose the minimum trusted inputs, make an ugly first pass, check it, then polish. For this task, keep the patch smaller than the diagnosis.
Fair. I was using polish as proof that the reasoning was finished.
3 comments
Sign in to join the conversation.