SZEYAN / THOUGHTS

← sz3yan.com

Thoughts

The build log behind SZEJO — what broke, what I decided, and what shipped.

  1. ·#szejo·5 min

    Three days, three silent failures — what a directory move actually breaks

    Symptom There wasn't one. That's the whole story. I reorganised the directory layout of a platform repo. The code moved, the tests passed, the site stayed up, and nothing in any log said otherwise…

  2. ·#szejo·3 min

    Every part of the pipeline worked. CI could not see its input.

    Symptom. A publishing pipeline had been built the day before: write a post in a directory, flip a flag in its frontmatter, push, and a workflow mirrors it into another repository that rebuilds the…

  3. ·#szejo·2 min

    The type-checker said yes and the tests said nothing, because I never asked them

    Symptom. None. That is the whole problem. I rewrote a page's data layer after the architecture underneath it changed — services that had been standalone were now modules inside another service, one…

  4. ·#szejo·1 min

    >=20.9.0 is a floor, and floors don't stop you falling upward

    A brand-new Node release broke npm install on a project whose engines field swore it only needed =20.9.0 . The failure was a native addon refusing to compile — six C++ errors against V8 headers that…

  5. ·#szejo·1 min

    When your own secret scanner is right and "it's just a placeholder" is the wrong answer

    Symptom. A routine commit, mid-restructure, gets blocked — a commit-time secret scanner flags what looks like a private key inside a Kubernetes manifest. Investigation. The key material was real, but…

  6. ·#szejo·2 min

    The one missing YAML line that made half our chat infra disappear

    Symptom. Two unrelated-looking features broke at once, on two different apps, days apart — a "Create Workspace" page in one internal tool, and a chat sidebar's live connection in another. Both errors…

  7. ·#szejo·2 min

    What actually happens to your data when your dev machine is the server

    Symptom. Not a bug report — a question. Running a real personal infrastructure stack entirely on one Mac's local Kubernetes cluster raises an obvious but easy-to-defer question: if this machine died…

  8. ·#szejo·1 min

    Trusting your own config file nearly cost me a login

    A CLI kept rejecting my credentials with "incorrect email or password." The password was right. The config file that stored the admin email had been right for months. It was not right any more…