Search for a command to run...
Last month I built a regression-testing harness for a single library upgrade — React Query v4 → v5 in one of the front-end apps I'm working on. It's about 800 lines of code across four packages. It ru
Images are heavy. When you're building offline support, storing them alongside your application data is tempting — and eventually painful. I hit this wall building support for image attachments. The n
Deciding how to approach offline support can be challenging, especially once you move beyond the basics. So far, I focused on persisting data that was already fetched as a result of user actions. This
Software engineering is changing faster than most of us can comfortably adapt to. The capabilities of LLM models change almost monthly. New tools appear every week. Advice that felt solid three months
This is the eighth post in my series about offline support in web applications and the fifth focused on the foreground queue. In the previous article, we covered error handling and retry strategies. A
This is the seventh post in the series about offline support in web applications and the fourth one focused specifically on the foreground queue. In the previous article, we exposed queue state, how UI components subscribe to it, and how to wire ever...
This is the sixth post in the series about offline support in web applications and the third one focused specifically on the foreground queue. In the previous article, we introduced the concept of a f
This is the fifth post in my series about offline support in web applications and the second one focused specifically on the foreground queue. In the previous article, I introduced a foreground queue for pending offline mutations and outlined its bas...
Deciding how to handle user actions when the network disappears is one of the trickiest parts of offline support. Reads are usually manageable once you have persistence in place. Writes are where things get interesting. This is the fourth post in my ...
