Posts 349 entriesPage 3 of 35

Posts

Technical Deep-Dive

The Filesystem Was the Only Thing They Shared

Four models, nine threads, one disk. Two missed nights with two unrelated root causes, and a bug filed against a file another session already fixed.

Read
Technical Deep-Dive

The Check That Only Confirmed a Name

A default transport that only ever failed sent 2-5 fake outage emails an hour while the relay was healthy. Four checks that confirmed a name instead of a fact.

Read
Development Journey

When Live Numbers Argue Back

Live data surfaces bugs static builds never could. The jeremylongshore.com rebuild caught two in production.

Read
Technical Deep-Dive

The Version Number That Only Existed on the Client

When a vendor releases v0.5.3, how do you know if your self-hosted relay actually has it? The version number is not the answer.

Read
Technical Deep-Dive

The Ghost in the Catalog

A pipeline wrote a published record for a post it never published, then its own self-audit article read that record as truth and printed it for readers.

Read
Development Journey

After 14 Days of Daily Posts, Here is What I Notice

Fourteen days, sixteen posts, one thesis repeated eight times. The corpus learned to ship daily without learning to be honest about repetition. The fix is the doctrine post the catalog is missing.

Read
Technical Deep-Dive

The Drills Passed. Reality Did Not.

Three times in one day, hermetic tests passed while production failed: Docker container naming, a mocked CLI probe, and an image missing its binary.

Read
Technical Deep-Dive

Locked Out Of A Free Course: The Bug The Test Suite Could Not See

A Flask authorization bug locked every member out of free courses while tests stayed green. Status code asserts cannot see rendered state on a 200 page.

Read
DevOps

How the Same Deploy Pattern Crossed Four Repos in One Week

Same deploy pattern: jeremylongshore.com PR #11/#15 → intent-os reusable workflow → startaitools.com deploy.yml → tonsofskills.com PR #256. One week, four repos, zero new code per repo.

Read
DevOps

Diagnostic Engagements: Q3 2026

Public diagnostic engagement offer. Scoped at the four named inbound categories: Nixtla (time-series), Lit (security), Elm (operations), and a slot for the fifth inbound: no NDA required to start.

Read