Tag: Systems Engineering

Browse our exclusive articles!

Merge Conflict vs CI Check: Why a Pull Request Can Be “Mergeable” but Red

Open a pull request and you may see something that looks like a contradiction: a green "This branch has no conflicts" line, and right below it a red ✗ on the checks. Both are true at once — because they are answering two completely different questions.

One Project, One Global Scope: The Apps Script Collision That Hides in Plain Sight

Two files in the same Apps Script project each declared a list called the same thing. The values matched, so everything worked — until the day someone edited one copy and not the other.

03/04 Is Two Different Dates: Parsing Ambiguity You Cannot See

An invoice date came through in a spreadsheet as 03/04/2026. That is March 4th, or April 3rd, and the value itself will never tell you which. Guess wrong and a payment looks a month early, or a month overdue, with no error anywhere.

Show People Clean Names, but Send Other Systems the Exact Values

Your contact form says "Referral". The CRM it feeds only accepts "Refferal", typo and all. Your visitors should never see that, and your form must still send it back letter for letter.

We Built CI Governance for a Team We Didn’t Have

Over a quarter we grew a careful set of governance workflows. Over a week we deleted almost all of them. The bill was the trigger — but the autopsy found something more useful than an overspend.

Popular

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

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

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

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

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