Regularly published articles on founder life, regulatory technology, and the nuances of AI and compliance.
Founder Notes
A guardrail denied some of my writes and allowed others. The split was clean and I had a mechanism to explain it. There was no rule — and I nearly widened a permission boundary to route around it.
Founder Notes
A report said two items were available to work on. The tracker agreed exactly. The same automation had already told the person both were blocked — in chat, where nothing it says becomes state.
Founder Notes
A deployed revision held a passing build that finished thirty-six seconds after publication. The evidence was true and it had authorised nothing. Certified is a claim about ordering, not a property of a revision.
Founder Notes
I wrote better versions of two instructions I had already given and could not withdraw either original. Replace is not a primitive: it is an add that always works plus a remove that sometimes does not.
Founder Notes
I reported our CI was completely broken. It had ten pipelines, all green. The command had answered honestly about one branch, and I carried the answer up to the project.
Founder Notes
The same useless error three times in one day, three different bugs. The reason was in the response body all along, and my own client was throwing it away.
Founder Notes
A file sat on our main branch for thirteen months and was never valid code. A formatter had tidied it along the way, and that grooming is part of why nobody questioned it.
Founder Notes
A field held a date and never said what kind of date it was. Everything downstream had to guess, and the layer that guesses is the one least able to hedge.
Founder Notes
My storage cleanup list was sorted by size, so I worked it from the top. The biggest item on it held the only copy of anything there.
Founder Notes
The official register for an industry is keyed on a physical asset. The firms I most wanted did not rank low in my list — they were never in it.
Showing 1-10 of 49 posts