Posts 324 entriesPage 1 of 33

Posts

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
DevOps

The Brand Behind the Plugins: A Survivorship Story

Why the plugin marketplace ran away. Lead with survivorship + the distribution gap, not the repo count. Tier 2 brand piece.

Read
DevOps

The Third State: When Your Checkout, Image, and Docker Volume All Disagree

A rebuild succeeded and nothing changed. How Docker named volumes shadow your image, and how to write a deploy smoke check that asserts on the served bytes.

Read
Development Journey

Now-LMS 2.0 and the Email Cutover

A 2.0.0 that is mostly a careful rename plus security headers is exactly what a healthy release looks like.

Read
DevOps

Splitting Privileges at the CI Boundary

Fork CI privilege separation in GitHub Actions prevents secret exfiltration. Run untrusted fork code and trusted deterministic steps safely.

Read
Architecture

Good mechanisms are not an architecture until a doctrine names them

You can ship a dozen good mechanisms and still have no architecture. A doctrine names why they cohere and forces every capability to fail closed.

Read