Notes from the work
What we learned building and running our own products, written up while it was still fresh. Mostly the things that went wrong, because those are the ones worth reading.
-
Boring on purpose
This site is static HTML with no JavaScript and no dependencies, built by a script we wrote. Here is the reasoning, and the bug that shows where the reasoning runs out. -
What AI actually changed about writing software
Generating code stopped being the slow part, which moved the bottleneck to verification. That is a bigger change to the job than it sounds, and we learned it the humiliating way. -
The check that looked at one column
An integrity check reported zero missing files, twice in one day, while nine files referenced by the database were genuinely gone. It was not wrong. It was narrow. -
A backup you have never restored is just a file
We added backups to a product that had none, then spent longer proving they worked than writing them. Four details that decide whether a backup is real. -
The bug that only happened half the time
Two environments shared a network. Service discovery quietly load-balanced production traffic into the wrong one, and the coin flip hid it for weeks.
Tell us what you need built.
Send us the problem in a paragraph — what your company does, and what the software should take off your hands. We will tell you honestly whether we are the right studio for it, and what it would take.
hello@synaptrixai.com