29 posts
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.
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...
Not every change needs the full test suite, and every change needs the safety gates. Here is how we let each push choose a fast or full pipeline witho...
Every function, command and component we add must be wired in and used in the same piece of work. Here is why we treat unused code as a defect, not a...
Sometimes the only way to understand a problem is to look at the live system. Here is how we inspect production safely, and why we never fix anything...
New frameworks appear every month. Here is why we build on mature, well-documented tools and spend our creativity on the problems our customers actual...
Many people and AI sessions often work in the same codebase at once. Here are the habits that keep their changes from colliding or erasing each other'...
A general AI assistant gives general answers. Here is how we use focused specialist roles, each with its own checklist, boundaries and freshness revie...
AI coding assistants help us move faster, but they never decide on their own what ships. Here is how we pair them with written rules and human review.
Some Jag Journey products cost nothing and never will. Here is why we build free software, how it is funded and what free means in practice.
Jag Journey is a small company with a large platform and several products. Here are the habits that make that possible without cutting corners.