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 →- Skip boilerplate sources and leftover source wordsA rewrite pipeline is only as good as what you feed it. Drop paywall and disclaimer text before the model runs, and flag leftover source-language words in code after.
- Make one-time redemptions safe to retryA one-time code that fails halfway is worse than a slow one. Claim it with a short lock, key retries with a client submission id, and return the original result instead of creating a second booking.
- Run local-time jobs on a UTC-only cronMost schedulers only speak UTC, and daylight saving time moves your users twice a year. Fire at both possible UTC times, decide in code, and make the job safe to run twice.
- Treat Postgres RLS as the security boundaryA filter in your app code is a suggestion an attacker will not send. Put ownership in Postgres with Row Level Security, prove it with an API call that skips the UI, and treat middleware as UX.
- Check LLM output in code, then retry exactly onceA limit written into a prompt is a wish, not a rule. Measure the output in code, feed the problems back for one rewrite, and decide up front what a failure that survives means.