How Jag Journey, LLC designs, builds, tests and ships its own software, and the principles behind each decision.
100 posts
Jag Journey is a small company with a large platform and several products. Here are the habits that make that possible without cutting corners.
AI models are confident even when they are wrong. Here is how we design AI features to work from approved sources, admit gaps and hand off to people i...
Nobody should wait for a newsletter to send before a page responds. Here is how we decide what runs immediately, what goes to a queue and how people s...
A backup that was queued, interrupted or never checked is not protection. Here is the standard we use before we call anything a recovery point.
When a website moves or a page changes address, every old link is a promise. Here is how we map old addresses to new ones so visitors and search engin...
When a request to an outside service ends without a clear answer, retrying can buy the same thing twice. Here is how we lock uncertain outcomes until...
A platform with many modules can feel like many different products. Here is how one admin design standard keeps every screen familiar, accessible and...
Two organizations can both have a page called About. Here is how composite unique keys keep addresses unique inside each account without blocking othe...
When a payment route is unavailable, it is tempting to quietly try another one. Here is why our payment code stops and says so instead, and what that...
There is always more to build than time to build it. Here is how we weigh customer needs, risk, purpose and maintenance when choosing what comes next.
Everyone wants to be cited by AI assistants. Here is what genuinely helps, from crawlable pages to truthful structured data, and the tricks we refuse...
Deferred work tends to become forgotten work. Here is why we complete requested work in the same session, and how we handle real blockers when they ap...