Colton Pomeroy
I build and ship software products, end to end, across emergency management, consumer mobile apps, games, and language-learning tools, plus websites for clients. Full-stack, whatever the stack needs to be. This is where I write about what I'm shipping, most days.
Latest posts
All posts →- Retry the reads, not the writes, and never read an outage as emptyA scheduled job that dies on one network blip is fragile, and one that treats a failed read as an empty answer is dangerous. Retry safe reads a few times, then fail loudly.
- Make your content guard check new fields by defaultA content rule that only checks the fields you listed goes blind the day someone adds a field. Walk every string and keep the exemptions on a short allowlist instead.
- Fail closed when guest progress cannot merge into an accountGuest study data in localStorage only becomes account data after every lookup and write succeeds. Skip marking the merge done when anything is missing.
- Put every verification rule into the generation prompt tooA checker that catches invented years and hardened claims is only half the fix. Encode those same rules in the prompt so the first draft passes more often.
- Enforce a WIP limit where the count goes up, not where work startsA work in progress cap checked at the wrong step can freeze a queue that is full of ready work. Put the limit on the transition that actually raises the count.