Tag: Systems Engineering

Browse our exclusive articles!

1,800 CI Minutes for 680 Minutes of Work: Where a Free-Tier Budget Actually Goes

Developer Operations Bosonica Bosonica -
A continuous-integration bill is not a speed problem. It is a counting problem — and almost every instinct you have about making builds cheaper is aimed at the wrong variable.

How to Run an Old Laptop as a Server — Without It Sleeping on You

Developer Operations Bosonica Bosonica -
A spare laptop makes a fine always-on machine. The reason it keeps dying isn't the hardware — it's three power defaults written for a device someone carries, not one that lives on a shelf.

Your Postgres Connection Limit Is Not Your Concurrency Limit

Developer Operations Bosonica Bosonica -
A database that accepts a hundred connections is not a database that does useful work on a hundred things at once. On a four-core box, throughput stopped scaling at four — and the fix was to stop counting connections and start counting cores.
1...567Page 7 of 7

Popular

Many-to-One: Why a Mapping Backlog Outgrows Its Target Taxonomy

Knowledge Systems 0
You're mapping a messy source vocabulary onto a clean target taxonomy. The target has about 5,600 slots, so the job must be roughly 5,600 decisions — right? The backlog is already past 8,900, and still climbing.

The Fix That Didn’t Take: When a Content-Hash Gate Skips Your Code Change

Developer Operations 0
You shipped a fix to how one field is computed, re-ran the pipeline across everything, and it reported a clean run. Then the consistency check still flags those records as wrong. The fix is in the code, the rebuild "ran" — and the records never changed. Your own optimisation skipped them.

Your Dedup Scan Is Over-Counting — Because It Forgot What You Already Fixed

Developer Operations 0
The report said 80 duplicate groups still to resolve. You'd been resolving them for days. You run it again after a big batch and it *still* says 80-ish. The backlog isn't stubborn — the scan is counting work you already finished.

When Your Skills Folder Is a Deploy Target, Not a Drawer

Developer Operations 0
You hardened a skill in the repo, shipped the PR, and the agent kept loading the old one. Or you fixed the live skill by hand, and the versioned copy quietly stayed behind. Same root cause: the copy you run and the copy you version are two different files.

Subscribe