Designing software for unreliable networks
Draft — placeholder content
Placeholder note. This page is scaffolding to demonstrate the notes layout. The real article is on its way — nothing here should be quoted as fact yet.
Draft outline
- Assuming the network is a constraint, not a given
- Optimistic updates and offline-first thinking
- What a 200 OK actually means on a weak connection
- Design patterns that survive a dropped request
TODO: Write the full article.