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 →- Turn a risky feature on only when the flag says exactly trueAn environment flag that guards money or personal data should default to off, accept one exact value for on, and be checked on the server where the work happens.
- Split a slow request into pages, but a short page is not the last pageWhen one big API request keeps timing out, fetching the same set in smaller pages helps. Just do not stop at the first short page if the server filters after it queries.
- Check each difficulty level against its neighbor, not just a targetEach difficulty level can hit its own target while the ladder is still upside down. Measure the step between neighbors and feed it back as a revision hint.
- Accept the answer without the accents, then show the real spellingWhen people type answers on a phone, missing accents are a keyboard problem, not a knowledge problem. Fold both sides before comparing, count it as right, and show the exact spelling.
- 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.