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 →- Put a timeout on every child process your script spawnsA shelled out command with no timeout can stall an entire automation run. Bound each one, keep going on failure, and make the dangerous failures loud.
- Let one manifest decide which pages get special treatmentWhen a handful of pages need different behavior, derive that set from the data file you already maintain instead of keeping a second list that drifts.
- Make your document generator refuse instead of guessingA script that turns your content into printable PDFs should stop loudly on bad input. Gate sensitive topics, check counts, and make the override explicit.
- Seed your demo data through the same code your users runA sales demo is only convincing if its data is real enough to break. Build it with your app's own actions, cover the messy cases on purpose, and make the command safe to rerun.
- Plan for a database host that refuses your triggersCheap managed MySQL often blocks triggers and fine-grained grants. Find out before deploy day, make the migration record what it got, and keep a check that works without them.