Engineering notes.
Short writeups on how we build and operate software, published so clients and partners can see how we think.
- July 23, 2026
How we keep AI-generated code reviewable
More of the code we ship starts as a prompt than a keystroke. That doesn't lower the bar for review — it raises it. Here are the standards, habits, and guardrails we use so AI-assisted work stays something a human can actually vouch for.
- June 23, 2026
How we onboard onto an existing codebase
What happens when a client brings us a system that already exists: the first-week audit, how we triage tech debt from real risk, and the principles that keep us from rewriting things that don't need rewriting.
- May 20, 2026
How we hand off code at the end of an engagement
What enterprise buyers actually get when a Courtix engagement wraps: source ownership from day one, written runbooks, architecture decision records, a live walkthrough and a 30-day warranty tail.
- April 18, 2026
How we pick a technology stack for a client
A languages-first view of stack selection: why we default to TypeScript, React and Python, how we choose between Cloudflare and AWS, and the questions we ask before committing to anything exotic.
- April 16, 2026
How we run incidents and post-mortems at Courtix
The operational half of shipping software: how we detect, triage, communicate, and learn from production incidents, with a 24-hour client notification SLA and a blameless review for every major event.
- April 14, 2026
How we scope a new engagement at Courtix
What the first two weeks of a Courtix engagement actually look like: discovery, written scope, the choice between fixed-price and time-and-materials, and the deliverables we hand over before any code ships.
- April 10, 2026
How we ship software to production at Courtix
A walk through our day-to-day engineering workflow: trunk-based development, protected main, CI gates and the release rituals that let a small team move quickly without breaking things.