Day 19/90: Async TypeScript
The useful shift today was making async state and failure explicit. I kept the lesson tied to three checks: decide which work can run in parallel and which work must stay sequenced, make loading and failure states explicit in the type model, and treat cancellation, retries, or backpressure as part of the design instead of afterthoughts.
The mistake worth catching early is treating async code as just syntax sugar and ignoring sequencing or failure propagation.…
