How Jag Journey, LLC designs, builds, tests and ships its own software, and the principles behind each decision.
100 posts
Moving an organization's website from another platform is never a single button press. Here is the backup, import, compare and repeat loop we use unti...
AI features cost money and touch customer data, so we keep a registry of every one. Here is how a call that is not on the list is refused before anyth...
An error message is often the moment someone decides whether to keep trusting software. Here is how we write messages that explain what happened and w...
Live video cannot be edited after the fact. Here is how we designed kill switches at the channel and platform level, who can use them and when they ac...
The best time to stop a bug from coming back is right after you fix it. Here is how we turn fixes into checks and what we learn from each one.
AI models change every few months, and yesterday's best choice can quietly become outdated. Here is how we keep model choices current without breaking...
Work is often continued by someone else: a teammate, a later session or an AI helper. Here is what our handoff notes contain so nothing important is l...
When an organization sells through our platform, the money should land in its own account. Here is how connected accounts, platform fees, refunds and...
AI can produce a full website draft or article in minutes. Here is why we treat every AI result as a draft until a person reviews it and chooses to pu...
When something changes unexpectedly, the first question is who changed it and when. Here is how audit trails answer that question without becoming a p...
Some organizations run more than one website. Here is how our platform keeps each site's pages, forms, files and domains separate inside a single acco...
Search engines cannot rank pages they have not found. Here is how our sitemaps list every public page and image, and how instant change notices speed...