[{"data":1,"prerenderedAt":722},["ShallowReactive",2],{"post-\u002Fblog\u002Fthe-knock-and-the-axe":3,"blog-all":221},{"id":4,"title":5,"author":6,"body":7,"category":202,"date":203,"description":204,"draft":205,"extension":206,"image":207,"meta":208,"navigation":209,"path":210,"project":211,"readingMinutes":212,"seo":213,"series":214,"seriesOrder":214,"stem":215,"tags":216,"__hash__":220},"blog\u002Fblog\u002Fthe-knock-and-the-axe.md","The Knock and the Axe","EkoHacks Team",{"type":8,"value":9,"toc":196},"minimark",[10,14,17,22,25,37,40,44,47,53,56,60,70,73,80,86,92,98,101,105,108,166,169,189,192],[11,12,13],"p",{},"There is a corner of EkoLite, our small real time backend, that most visitors would walk straight past: the shutdown. On a signal it closes the websocket, then the Mongo connection, then exits, and if any of that hangs past five seconds it exits hard with a code that says so. All of it tested, none of it complicated. Which invites a fair question. The project has no production deployment yet, so where is any of this actually useful?",[11,15,16],{},"The answer needs a short detour into what an operating system does when it wants your process gone. It has two instruments, and they could not be less alike.",[18,19,21],"h2",{"id":20},"sigterm-the-knock","SIGTERM, the knock",[11,23,24],{},"Signals are the oldest messaging system on Unix: tiny numbered notifications the kernel delivers to a process. SIGTERM is the polite one. It means please stop, and crucially, the process is allowed to hear it. You register a handler, and when the signal arrives you get to run code: finish the request you were serving, flush what you were writing, say goodbye to your database, choose your own exit code.",[11,26,27,28,32,33,36],{},"You have already sent this signal thousands of times. Ctrl+C in a terminal sends SIGINT, its interactive sibling. ",[29,30,31],"code",{},"kill \u003Cpid>"," sends SIGTERM by default. ",[29,34,35],{},"docker stop"," sends SIGTERM. When Kubernetes moves a pod, scales a deployment down, or drains a node, the first thing your container hears is SIGTERM.",[11,38,39],{},"The key word in every one of those sentences is first. SIGTERM is not a command, it is an opening offer. The sender starts a clock the moment it knocks.",[18,41,43],{"id":42},"sigkill-the-axe","SIGKILL, the axe",[11,45,46],{},"SIGKILL is the other instrument, and the difference is absolute: it cannot be caught, handled, or delayed. The kernel does not deliver it to your process, it removes your process. No handler runs. No flush happens. No exit code of yours is recorded, the process simply stops existing between one instruction and the next.",[11,48,49,50,52],{},"The two are joined by that clock. ",[29,51,35],{}," knocks, waits ten seconds, then swings the axe. Kubernetes knocks, waits thirty by default, then swings. So every process that runs under an orchestrator lives with the same contract: you have a fixed window between the knock and the axe, and whatever you wanted to say needs saying inside it.",[11,54,55],{},"This is why our shutdown has a five second deadline of its own. If the goodbye hangs, we would rather exit 1 in our own words, inside the window, than be erased mid sentence after it. The polite window is exactly the space in which graceful shutdown exists. Ignore the knock and the axe makes the decision for you.",[18,57,59],{"id":58},"why-build-it-before-the-deployment","Why build it before the deployment",[11,61,62,63,66,67,69],{},"Here is the part that answers the fair question. Shutdown is not a thing you bolt on once you have somewhere to deploy. It is a property of running under anything that can stop you, and everything can stop you. ",[29,64,65],{},"kill"," on a laptop, ",[29,68,35],{}," in a compose file, a scale down in an orchestrator: every one of them opens with SIGTERM. So shutdown is not something that happens when things go wrong. It is something that happens as part of things going right, dozens of times over the life of a service. Every restart is a shutdown. Building it now, as a feature with tests, is putting the seam where the need already is, so the deploy that arrives later hangs off a shutdown that already works rather than one written in a panic.",[11,71,72],{},"And EkoLite holds exactly the kinds of state that make an axe murder expensive:",[11,74,75,79],{},[76,77,78],"strong",{},"Live sockets."," Clients hold open websocket connections for their subscriptions. Close the socket properly and the client sees a clean close frame and reconnects on its own terms. Die to SIGKILL and every client sees a network fault instead, which is a different and worse code path in every client ever written.",[11,81,82,85],{},[76,83,84],{},"A database mid conversation."," Our close order is deliberate: socket first, so no new requests arrive, then Mongo. Reverse it, or skip it, and requests in flight are talking to a database that vanished from under them.",[11,87,88,91],{},[76,89,90],{},"A pipeline with a write back."," An app method can resolve an uploaded file, run an analysis script, and write the result back so it streams to every subscriber. A SIGTERM in the middle of that is the genuinely interesting case, because the result is the product. If shutdown hangs there and times out, our exit 1 in the logs is the first breadcrumb when someone asks where their result went. SIGKILL leaves no breadcrumb at all.",[11,93,94,97],{},[76,95,96],{},"An honest gap the work exposed."," Writing the shutdown policy made something visible: an analysis child process is not in the close graph. A SIGTERM during a run orphans that child today, and its result never lands. That is not a hole in the new code so much as a question the code can finally ask. Before, what happens to a half finished analysis on deploy was not answerable anywhere. Now there is a tested shutdown policy with an obvious place for the answer, and that is a story for another day.",[11,99,100],{},"There is a quieter benefit too. Exit codes are the one sentence a process gets to leave behind, and orchestrators read them. Exit 0, clean stop, nothing to see. Exit 1 with a timestamp, a shutdown gave up, go look. A fleet that shuts down cleanly and says so is what operational maturity looks like from up close, and it is the sort of boring evidence that decides whether people trust you to run their infrastructure.",[18,102,104],{"id":103},"the-move-you-can-reproduce","The move you can reproduce",[11,106,107],{},"You do not need an orchestrator to feel the difference between the knock and the axe. Start the server and knock politely:",[109,110,115],"pre",{"className":111,"code":112,"language":113,"meta":114,"style":114},"language-bash shiki shiki-themes github-dark","npm run dev:server        # listens on :3001\n# in another shell, or just press Ctrl+C in the server's own\nkill -TERM \u003Cpid>\n","bash","",[29,116,117,137,143],{"__ignoreMap":114},[118,119,122,126,130,133],"span",{"class":120,"line":121},"line",1,[118,123,125],{"class":124},"svObZ","npm",[118,127,129],{"class":128},"sU2Wk"," run",[118,131,132],{"class":128}," dev:server",[118,134,136],{"class":135},"sAwPA","        # listens on :3001\n",[118,138,140],{"class":120,"line":139},2,[118,141,142],{"class":135},"# in another shell, or just press Ctrl+C in the server's own\n",[118,144,146,149,152,156,159,163],{"class":120,"line":145},3,[118,147,65],{"class":148},"sDLfK",[118,150,151],{"class":148}," -TERM",[118,153,155],{"class":154},"snl16"," \u003C",[118,157,158],{"class":128},"pi",[118,160,162],{"class":161},"s95oV","d",[118,164,165],{"class":154},">\n",[11,167,168],{},"Watch the log. It closes the socket, then Mongo, then exits with code 0, in that order, on purpose. Now start it again and swing the axe instead:",[109,170,172],{"className":111,"code":171,"language":113,"meta":114,"style":114},"kill -KILL \u003Cpid>\n",[29,173,174],{"__ignoreMap":114},[118,175,176,178,181,183,185,187],{"class":120,"line":121},[118,177,65],{"class":148},[118,179,180],{"class":148}," -KILL",[118,182,155],{"class":154},[118,184,158],{"class":128},[118,186,162],{"class":161},[118,188,165],{"class":154},[11,190,191],{},"Nothing. No goodbye, no ordered close, no exit code of its own, not a line in the log. The process was there and then it was not. That gap between the two runs is the whole feature: SIGTERM is a request your code can hear and answer, SIGKILL is a removal your code never sees. Graceful shutdown is not about crashes. It is what your process does with the fixed window it is given, every ordinary time something asks it to stop.",[193,194,195],"style",{},"html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html pre.shiki code .snl16, html code.shiki .snl16{--shiki-default:#F97583}html pre.shiki code .s95oV, html code.shiki .s95oV{--shiki-default:#E1E4E8}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":114,"searchDepth":139,"depth":139,"links":197},[198,199,200,201],{"id":20,"depth":139,"text":21},{"id":42,"depth":139,"text":43},{"id":58,"depth":139,"text":59},{"id":103,"depth":139,"text":104},"Shipping and Operations","2026-07-20T12:00:00.000Z","SIGTERM is a request your process can hear and SIGKILL is removal it never sees, and the fixed window between them is exactly where graceful shutdown lives.",false,"md","\u002Fimages\u002Fblog\u002Fthe-knock-and-the-axe-hero.jpg",{},true,"\u002Fblog\u002Fthe-knock-and-the-axe","EkoLite",6,{"title":5,"description":204},null,"blog\u002Fthe-knock-and-the-axe",[217,218,219],"shutdown","operations","signals","BT3Hxe9lroyTuU8KVumnrOlzW_yMxNm0AZyXnXPe1so",[222,234,245,253,264,271,280,287,294,303,311,320,327,334,347,356,363,370,379,387,395,405,412,420,427,433,439,448,456,466,474,481,492,500,506,516,525,533,540,548,556,563,565,573,580,586,593,602,610,617,624,633,639,647,653,661,667,676,683,690,698,704,710,716],{"path":223,"title":224,"description":225,"date":226,"author":6,"image":227,"readingMinutes":212,"category":228,"project":229,"tags":230,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fa-branch-is-inventory","A Branch Is Inventory","Unintegrated code is stock in a warehouse, and it depreciates. Our branch was one merge behind the trunk and that was enough for a conflict. What waiting costs.","2026-07-09T09:38:00.000Z","\u002Fimages\u002Fblog\u002Fa-branch-is-inventory-hero.jpg","Craft and Practice","The Dojo",[231,232,233],"git","continuous-integration","craft",{"path":235,"title":236,"description":237,"date":238,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":241,"draft":205,"series":244,"seriesOrder":145},"\u002Fblog\u002Fa-map-drawn-by-the-build","A Map Drawn by the Build","Thirty six of our pages had never been visited by Google because nothing said they existed. The sitemap is drawn from the build, and it found a draft.","2026-08-22T20:30:00.000Z",7,"ekohacks.com",[242,218,243],"seo","nuxt","From Invisible to Findable",{"path":246,"title":247,"description":248,"date":249,"author":6,"image":214,"readingMinutes":212,"category":202,"project":240,"tags":250,"draft":205,"series":244,"seriesOrder":252},"\u002Fblog\u002Fa-privacy-policy-you-can-diff","A Privacy Policy You Can Diff","Our legal pages are files in the same repository as the site. Each now lists every change to its text, with the date and the diff, drawn from git at build time.","2026-08-23T16:00:00.000Z",[251,218,243],"privacy",9,{"path":254,"title":255,"description":256,"date":257,"author":6,"image":258,"readingMinutes":239,"category":259,"project":211,"tags":260,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fan-off-switch-not-a-disguise","An Off Switch, Not a Disguise","A Nullable differs from a stub in whether production code can tell the fake is there. Finding the word fixed a socket wrapper that had been lying to its tests.","2026-07-20T09:05:00.000Z","\u002Fimages\u002Fblog\u002Fan-off-switch-not-a-disguise-hero.jpg","Testing and TDD",[261,262,263],"nullables","testing","websocket",{"path":265,"title":266,"description":267,"date":268,"author":6,"image":269,"readingMinutes":270,"category":228,"project":214,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fbuilding-engineering-teams-that-learn-together","Building Engineering Teams That Learn Together","The strongest engineering teams are not the ones with the most talented individuals. They are the ones that have learned how to learn together.","2026-02-05T09:00:00.000Z","\u002Fimages\u002Fblog\u002Fteams-that-learn-together-hero.jpg",4,{"path":272,"title":273,"description":274,"date":275,"author":6,"image":276,"readingMinutes":270,"category":202,"project":229,"tags":277,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fderived-state-recompute","The Fix Was Merged, but the Numbers Were Still Wrong","We fixed a scoring bug, reviewed it, merged it, and production still showed the old numbers. Derived data is a cache that goes stale, and it must be recomputed.","2026-07-08T21:43:55.000Z","\u002Fimages\u002Fblog\u002Fderived-state-recompute-hero.jpg",[218,278,279],"deployment","idempotency",{"path":281,"title":282,"description":283,"date":284,"author":285,"image":286,"readingMinutes":212,"category":202,"project":214,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fdockerising-nestjs-nuxt-monorepo-with-pnpm","Dockerising a NestJS and Nuxt Monorepo with pnpm","Dockerising a NestJS and Nuxt monorepo with pnpm: separate multi stage Dockerfiles for development and production, one Compose file, reproducible environments.","2026-02-09T09:00:00.000Z","Ogochukwu Okpala","\u002Fimages\u002Fblog\u002Fdocker-monorepo-hero.png",{"path":288,"title":289,"description":290,"date":291,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":292,"draft":205,"series":244,"seriesOrder":293},"\u002Fblog\u002Ffifty-posts-and-an-empty-robots-txt","Fifty Posts and an Empty robots.txt","Our site scored 100 for SEO and nobody could find it. The audit that started a series on making a site findable, and on what measuring visitors costs them.","2026-08-21T14:30:00.000Z",[242,218,233],0,{"path":295,"title":296,"description":297,"date":298,"author":6,"image":299,"readingMinutes":270,"category":228,"project":229,"tags":300,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ffrom-convention-to-plugin","From Convention to Plugin","A five step procedure for webhook signature checks, easy to forget and silent when you did, became one Fastify plugin. The safe path is now impossible to skip.","2026-04-17T08:26:12.000Z","\u002Fimages\u002Fblog\u002Ffrom-convention-to-plugin-hero.jpg",[233,301,302],"fastify","security",{"path":304,"title":305,"description":306,"date":307,"author":6,"image":308,"readingMinutes":309,"category":202,"project":229,"tags":310,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fintegrate-against-the-trunk","Integrate Against the Trunk, Not Your Copy of It","A rebase onto a stale local main succeeds, looks resolved, and leaves the pull request conflicting. Everything on your machine is a photograph of the trunk.","2026-07-09T09:22:00.000Z","\u002Fimages\u002Fblog\u002Fintegrate-against-the-trunk-hero.jpg",5,[231,232,218],{"path":312,"title":313,"description":314,"date":315,"author":6,"image":316,"readingMinutes":270,"category":228,"project":229,"tags":317,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Flandmines","Landmines","Most CLAUDE.md files grow because documenting a convention feels like progress. Ours holds landmines only: facts the code cannot tell you, costly to step on.","2026-04-17T10:15:06.000Z","\u002Fimages\u002Fblog\u002Flandmines-hero.jpg",[233,318,319],"documentation","ai-agents",{"path":321,"title":322,"description":323,"date":324,"author":6,"image":325,"readingMinutes":212,"category":202,"project":229,"tags":326,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fnever-break-the-build","Never Break the Build","If the software worked five minutes ago, only five minutes of change can be to blame. What a green trunk buys, who pays for it, and a check that could not fail.","2026-07-09T09:54:00.000Z","\u002Fimages\u002Fblog\u002Fnever-break-the-build-hero.jpg",[232,218,262],{"path":328,"title":329,"description":330,"date":331,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":332,"draft":205,"series":244,"seriesOrder":139},"\u002Fblog\u002Fone-address-per-page","One Address per Page","Every page on our site answered with a redirect before it answered with a page. How we made the build emit one address, declare it, and check it live.","2026-08-22T18:30:00.000Z",[242,218,243,333],"netlify",{"path":335,"title":336,"description":337,"date":338,"author":6,"image":339,"readingMinutes":270,"category":340,"project":341,"tags":342,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fone-command-three-policies","One Command, Three Policies, Zero Duplication","Preflight, cut and ship each worked alone before one command composed them. Why the composition layer is forty lines, and how the scrollback became the record.","2026-07-21T17:20:00.000Z","\u002Fimages\u002Fblog\u002Fone-command-three-policies-hero.jpg","Design and Architecture","The EkoHacks CLI",[343,344,345,346],"composition","cli-design","narration","encoding-the-release",{"path":348,"title":349,"description":350,"date":351,"author":6,"image":352,"readingMinutes":239,"category":340,"project":211,"tags":353,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fone-way-to-fail","One Way to Fail","Closing the convergence so an upload fails in the same error shape as every other call, mostly by deleting the code that made the two shapes differ.","2026-07-20T10:05:00.000Z","\u002Fimages\u002Fblog\u002Fone-way-to-fail-hero.jpg",[354,261,355],"design","error handling",{"path":357,"title":358,"description":359,"date":360,"author":6,"image":361,"readingMinutes":212,"category":202,"project":229,"tags":362,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fready-to-ship-not-ready-to-release","Ready to Ship, Not Ready to Release","Most teams hide a delay between saying done and being able to ship. Being ready to release at any moment, and why our deploy ships the commit that was tested.","2026-07-09T10:02:00.000Z","\u002Fimages\u002Fblog\u002Fready-to-ship-hero.jpg",[232,278,218],{"path":364,"title":365,"description":366,"date":367,"author":6,"image":368,"readingMinutes":212,"category":228,"project":229,"tags":369,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Frebase-or-merge-is-the-wrong-argument","Rebase or Merge Is the Wrong Argument","Both commands reconcile the same commits and hit the same conflicts. What differs is when you resolve them. The loud argument hides a quiet one: long branches.","2026-07-09T09:30:00.000Z","\u002Fimages\u002Fblog\u002Frebase-or-merge-hero.jpg",[231,232,233],{"path":371,"title":372,"description":373,"date":374,"author":6,"image":375,"readingMinutes":145,"category":340,"project":229,"tags":376,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Freconstructing-the-past","Reconstructing the Past","Connect a repository with a year of history and a trend curve reaches back months. How a system shows a past it never saw, recomputed from one source of truth.","2026-07-07T21:26:35.000Z","\u002Fimages\u002Fblog\u002Freconstructing-the-past-hero.jpg",[354,377,378],"data","onboarding",{"path":380,"title":381,"description":382,"date":383,"author":6,"image":214,"readingMinutes":212,"category":259,"project":341,"tags":384,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fretiring-a-board","Retiring a Board: User Testing a CLI Before You Ship It","An afternoon of user testing against a real Linear board, and the four findings a green test suite could never have written.","2026-08-01T10:20:00.000Z",[385,261,344,386],"user-testing","linear",{"path":388,"title":389,"description":390,"date":391,"author":6,"image":392,"readingMinutes":309,"category":259,"project":229,"tags":393,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fretrofitting-testing-without-mocks","Retrofitting Testing Without Mocks","The server had 37 vi.mock calls and no test that touched the database. Five steps to remove every mock with Nullables: real logic, real data, sociable tests.","2026-04-17T12:30:37.000Z","\u002Fimages\u002Fblog\u002Fretrofitting-without-mocks-hero.jpg",[262,261,394],"mocks",{"path":396,"title":397,"description":398,"date":399,"author":6,"image":400,"readingMinutes":270,"category":202,"project":341,"tags":401,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Frun-it-by-hand-until-it-is-boring","Run It by Hand Until It Is Boring","Releasing EkoLite was a document before it was a command, and stayed one until running it by hand had nothing left to teach us. Why we automate operations last.","2026-07-21T17:00:00.000Z","\u002Fimages\u002Fblog\u002Frun-it-by-hand-hero.jpg",[402,403,404,346],"automation","releasing","process",{"path":406,"title":407,"description":408,"date":374,"author":6,"image":409,"readingMinutes":145,"category":202,"project":229,"tags":410,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fsafe-to-run-twice","Safe to Run Twice","Connect the same repository twice, or let a webhook redeliver an event. Idempotency in two halves: writes through a natural key, side effects behind a ledger.","\u002Fimages\u002Fblog\u002Fsafe-to-run-twice-hero.jpg",[218,279,411],"webhooks",{"path":413,"title":414,"description":415,"date":416,"author":6,"image":214,"readingMinutes":212,"category":202,"project":229,"tags":417,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fsource-or-execute","Source or Execute","Our dojo laptops are provisioned by one bash script of nearly twelve hundred lines. Splitting it into modules is two decisions, not one, and we chose a hybrid.","2026-08-01T09:00:00.000Z",[418,419,343,218],"shell","provisioning",{"path":421,"title":422,"description":423,"date":214,"author":424,"image":425,"readingMinutes":121,"category":340,"project":426,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fstage-then-transform-why-your-crawler-should-never-touch-production-tables","Stage, Then Transform: Crawlers Stay Out of Production","Where data from an external source lands first decides whether the pipeline still works in six months. The staging pattern, shown with a crawler we build now.","EkoHacks","\u002Fimages\u002Fblog\u002Fstage-then-transform-hero.jpg","Propi",{"path":428,"title":429,"description":430,"date":431,"author":6,"image":214,"readingMinutes":239,"category":259,"project":240,"tags":432,"draft":205,"series":244,"seriesOrder":309},"\u002Fblog\u002Ftelling-the-machine-what-the-page-is","Telling the Machine What the Page Is","Structured data on every post, and a test that runs after each build and fails it when a page lacks what a crawler needs. First run: forty nine problems.","2026-08-22T23:30:00.000Z",[242,262,243],{"path":434,"title":435,"description":436,"date":437,"author":6,"image":438,"readingMinutes":139,"category":259,"project":214,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ftest-driven-development-is-not-about-tests","Test Driven Development Is Not About Tests","TDD is widely misunderstood. It is not a testing strategy. It is a design tool that produces simpler, more focused code by making you think before you type.","2026-02-01T09:00:00.000Z","\u002Fimages\u002Fblog\u002Ftdd-not-about-tests-hero.jpg",{"path":440,"title":441,"description":442,"date":443,"author":6,"image":444,"readingMinutes":309,"category":259,"project":341,"tags":445,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ftesting-a-release-without-releasing","Testing a Release Without Releasing","How to test watch CI until green, then merge, hundreds of times a day with no CI in sight. Nullables, output trackers, and a fake that copies GitHub shapes.","2026-07-21T17:10:00.000Z","\u002Fimages\u002Fblog\u002Ftesting-a-release-without-releasing-hero.jpg",[261,446,447,346],"testing-without-mocks","james-shore",{"path":449,"title":450,"description":451,"date":452,"author":6,"image":214,"readingMinutes":212,"category":259,"project":229,"tags":453,"draft":205,"series":455,"seriesOrder":121},"\u002Fblog\u002Fthe-best-coverage-number-in-the-room","The Best Coverage Number in the Room","Same commit, same spec, same test count. The mocked suite ran 5.6 times faster, covered 3.5 fewer points of real code, and posted the best branch coverage.","2026-08-27T12:00:00.000Z",[262,261,394,454],"coverage","What Mocks Cost",{"path":457,"title":458,"description":459,"date":460,"author":6,"image":461,"readingMinutes":309,"category":340,"project":211,"tags":462,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-bug-that-resolved-successfully","The Bug That Resolved Successfully","A bug that threw no error and dropped every document because the client guessed a collection from a name. The fix was one honest field on the ready message.","2026-07-05T10:16:16.000Z","\u002Fimages\u002Fblog\u002Fbug-resolved-successfully-hero.jpg",[463,464,262,465],"protocol","pubsub","tdd",{"path":467,"title":468,"description":469,"date":470,"author":6,"image":471,"readingMinutes":212,"category":259,"project":211,"tags":472,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-clock-that-learned-to-walk","The Clock That Learned to Walk","A stub clock that teleported to the end of the window instead of passing through time, so a timer set inside another never fired. A real clock model fixed it.","2026-07-07T22:44:42.000Z","\u002Fimages\u002Fblog\u002Fthe-clock-that-learned-to-walk-hero.jpg",[261,262,473],"refactoring",{"path":475,"title":476,"description":477,"date":478,"author":6,"image":479,"readingMinutes":309,"category":228,"project":229,"tags":480,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-conflict-nobody-wrote","The Conflict Nobody Wrote","A pull request conflicted in a file neither author had typed into. A generated document recorded test line numbers, both branches shifted them, git merges text.","2026-07-09T09:14:00.000Z","\u002Fimages\u002Fblog\u002Fthe-conflict-nobody-wrote-hero.jpg",[231,232,233],{"path":482,"title":483,"description":484,"date":485,"author":6,"image":486,"readingMinutes":487,"category":202,"project":229,"tags":488,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-container-that-wasnt-there","The Container That Wasn't There","Production served HTML where the browser asked for JavaScript, and nothing in our code had changed. A week debugging a platform we cannot see inside.","2026-07-17T14:30:00.000Z","\u002Fimages\u002Fblog\u002Fcontainer-that-wasnt-there-hero.jpg",8,[218,489,490,491],"debugging","european-tech","community",{"path":493,"title":494,"description":495,"date":496,"author":6,"image":497,"readingMinutes":212,"category":340,"project":211,"tags":498,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-design-we-never-drew","The Design We Never Drew","How the upload path in EkoLite arrived rather than being drawn, and the two habits, test first and integrate always, that turn an emerging shape into a design.","2026-07-20T10:00:00.000Z","\u002Fimages\u002Fblog\u002Fthe-design-we-never-drew-hero.jpg",[354,465,499],"continuous integration",{"path":501,"title":502,"description":503,"date":504,"author":6,"image":505,"readingMinutes":270,"category":228,"project":214,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-dojo-way-deliberate-practice-for-software-developers","The Dojo Way: Deliberate Practice for Software Developers","Most developers learn on the job, and the job rarely teaches the fundamentals. The Dojo borrows from martial arts to make a space for deliberate practice.","2026-01-22T09:00:00.000Z","\u002Fimages\u002Fblog\u002Fthe-dojo-way-hero.jpg",{"path":507,"title":508,"description":509,"date":510,"author":6,"image":511,"readingMinutes":239,"category":228,"project":229,"tags":512,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-done-column-is-a-syllabus","The Done Column Is a Syllabus","We asked Linear for every story our team has ever finished, all 187 of them, and read the column end to end. It turned out to be the course we teach.","2026-07-31T09:00:00.000Z","\u002Fimages\u002Fblog\u002Fdone-column-syllabus-hero.jpg",[513,514,515,386],"graphql","stories","xp",{"path":517,"title":518,"description":519,"date":520,"author":6,"image":521,"readingMinutes":309,"category":259,"project":341,"tags":522,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-failing-test-is-the-review","The Failing Test Is the Review","Every behaviour in the CLI landed as two commits: a red test, then the code that makes it green. Reviewing intent before implementation, and why red never bent.","2026-07-21T17:05:00.000Z","\u002Fimages\u002Fblog\u002Fthe-failing-test-is-the-review-hero.jpg",[465,523,524,346],"red-first","code-review",{"path":526,"title":527,"description":528,"date":529,"author":6,"image":530,"readingMinutes":309,"category":202,"project":341,"tags":531,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-first-real-run-said-no","The First Real Run Said No","The tool's first real outing ended with FAIL and a stopped rail, and we count it as a success. A naive sounding question then uncovered a quiet failure mode.","2026-07-21T17:25:00.000Z","\u002Fimages\u002Fblog\u002Fthe-first-real-run-said-no-hero.jpg",[403,532,231,346],"preflight",{"path":534,"title":535,"description":536,"date":537,"author":6,"image":538,"readingMinutes":309,"category":202,"project":211,"tags":539,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-five-second-goodbye","The Five Second Goodbye","A shutdown that arms its own deadline so a hung close cannot strand the process, with the policy lifted out of the boot shell so every decision can be tested.","2026-07-05T12:03:00.000Z","\u002Fimages\u002Fblog\u002Fthe-five-second-goodbye-hero.jpg",[217,261,262],{"path":541,"title":542,"description":543,"date":544,"author":6,"image":545,"readingMinutes":212,"category":202,"project":211,"tags":546,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-framework-in-the-description-field","The Framework in the Description Field","Our package called itself a framework, but it could not be installed. The fix was to stop trusting the build and become the stranger who installs the tarball.","2026-07-08T17:28:39.000Z","\u002Fimages\u002Fblog\u002Fframework-description-field-hero.jpg",[547,262,233],"packaging",{"path":549,"title":550,"description":551,"date":552,"author":6,"image":553,"readingMinutes":270,"category":340,"project":341,"tags":554,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-gate-always-asks","The Gate Always Asks","A release automates things you cannot take back, so which of them may a machine do without asking a human? Pauses, and a yes flag that opens no door.","2026-07-21T17:15:00.000Z","\u002Fimages\u002Fblog\u002Fthe-gate-always-asks-hero.jpg",[402,555,354,346],"human-in-the-loop",{"path":557,"title":558,"description":559,"date":560,"author":6,"image":561,"readingMinutes":212,"category":202,"project":229,"tags":562,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-gate-went-red-and-it-was-right","The Gate Went Red, and It Was Right","We added the missing check on our API specification and it failed on its first run, because the file was never a function of the source. A clean machine saw it.","2026-07-09T10:10:00.000Z","\u002Fimages\u002Fblog\u002Fgate-went-red-hero.jpg",[232,218,233],{"path":210,"title":5,"description":204,"date":203,"author":6,"image":207,"readingMinutes":212,"category":202,"project":211,"tags":564,"draft":205,"series":214,"seriesOrder":214},[217,218,219],{"path":566,"title":567,"description":568,"date":569,"author":6,"image":570,"readingMinutes":487,"category":228,"project":211,"tags":571,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-line-nothing-could-see","The Line Nothing Could See","Reviewing the reasoning under a refactor, not only the diff. Ask of every line what can observe it, and back each review claim with a test the author can run.","2026-07-07T22:43:00.000Z","\u002Fimages\u002Fblog\u002Fthe-line-nothing-could-see-hero.jpg",[524,473,572,262],"teaching",{"path":574,"title":575,"description":576,"date":577,"author":6,"image":578,"readingMinutes":212,"category":340,"project":211,"tags":579,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-long-way-round","The Long Way Round","The count a method computes reaches the screen not through its return value but by being written into a collection a client subscribes to, EkoLite's channel.","2026-07-20T11:05:00.000Z","\u002Fimages\u002Fblog\u002Fthe-long-way-round-hero.jpg",[354,464,261],{"path":581,"title":582,"description":583,"date":584,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":585,"draft":205,"series":244,"seriesOrder":121},"\u002Fblog\u002Fthe-page-that-existed-only-when-someone-linked-to-it","The Page That Existed Only When Someone Linked to It","Our blog vanished in production while passing every local check. How we found the cause, fixed it twice, and how the fix gave every page a twin.","2026-08-22T16:00:00.000Z",[242,218,243],{"path":587,"title":588,"description":589,"date":590,"author":6,"image":591,"readingMinutes":487,"category":202,"project":229,"tags":592,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-previews-that-served-production","The Previews That Served Production","Two weeks after the container that was not there, the same impossible error came back. The orphans were our own pull request previews. One diagnosis was wrong.","2026-07-31T17:00:00.000Z","\u002Fimages\u002Fblog\u002Fpreviews-served-production-hero.jpg",[218,489,490,491],{"path":594,"title":595,"description":596,"date":597,"author":6,"image":598,"readingMinutes":270,"category":228,"project":341,"tags":599,"draft":209,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-release-is-the-acceptance-test","The Release Is the Acceptance Test","Not a green suite, not a good demo: a real version of a real package, live on npm, shipped by the tool. What red first tests proved, and what only reality did.","2026-07-21T17:35:00.000Z","\u002Fimages\u002Fblog\u002Frelease-acceptance-test-hero.jpg",[403,600,601,346],"dogfooding","acceptance-testing",{"path":603,"title":604,"description":605,"date":606,"author":6,"image":607,"readingMinutes":239,"category":259,"project":211,"tags":608,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-script-that-never-ran","The Script That Never Ran","Joining two abilities EkoLite already had, a method that runs and a runner that shells out, and proving the join with a nulled runner before any script exists.","2026-07-20T11:00:00.000Z","\u002Fimages\u002Fblog\u002Fthe-script-that-never-ran-hero.jpg",[262,261,609],"scriptrunner",{"path":611,"title":612,"description":613,"date":614,"author":6,"image":214,"readingMinutes":487,"category":202,"project":240,"tags":615,"draft":205,"series":244,"seriesOrder":212},"\u002Fblog\u002Fthe-small-things-the-crawler-notices","The Small Things the Crawler Notices","Speed is the part of findability you can measure on a laptop. Fonts and images we shipped without looking, an error page we did not have, and the numbers after.","2026-08-23T10:00:00.000Z",[242,218,616],"performance",{"path":618,"title":619,"description":620,"date":621,"author":6,"image":622,"readingMinutes":239,"category":259,"project":211,"tags":623,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-test-that-could-not-fail","The Test That Could Not Fail","A green test that stayed green when we deleted the behaviour it was named after, and the single blunt question that exposed it.","2026-07-20T09:00:00.000Z","\u002Fimages\u002Fblog\u002Ftest-that-could-not-fail-hero.jpg",[262,261,263],{"path":625,"title":626,"description":627,"date":628,"author":424,"image":629,"readingMinutes":212,"category":228,"project":630,"tags":631,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-website-that-told-the-same-story-twice","The Website That Told the Same Story Twice","Our home and story pages felt like one story across two screens. Rather than argue by taste, we modelled our words as data and asked a database one question.","2026-06-06","\u002Fimages\u002Fblog\u002Fwebsite-same-story-twice-hero.jpg","The Website",[233,632,377,572],"content",{"path":634,"title":635,"description":636,"date":460,"author":6,"image":637,"readingMinutes":309,"category":259,"project":211,"tags":638,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-words-we-work-in","The Words We Work In","The vocabulary we test with, Nullable, embedded stub, stub object, output tracking, each grounded in real code so a review points at a line, never at taste.","\u002Fimages\u002Fblog\u002Fthe-words-we-work-in-hero.jpg",[261,262,233,572],{"path":640,"title":641,"description":642,"date":628,"author":424,"image":643,"readingMinutes":270,"category":228,"project":630,"tags":644,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fthe-workflow-is-the-lesson","The Workflow Is the Lesson","We are moving our content out of a cloud CMS and into git. Why a school that teaches a keyboard first way of working should practise it in the open, and how.","\u002Fimages\u002Fblog\u002Fworkflow-lesson-hero.png",[645,231,572,646],"workflow","accessibility",{"path":648,"title":649,"description":650,"date":651,"author":6,"image":214,"readingMinutes":212,"category":259,"project":229,"tags":652,"draft":205,"series":455,"seriesOrder":139},"\u002Fblog\u002Ftwenty-six-more-tests-four-fewer-behaviours","Twenty Six More Tests, Four Fewer Behaviours","Removing the mocks grew the suite from 44 tests to 70 and quietly deleted four behaviours, every one of them a failure path. Test count is not coverage.","2026-08-28T09:00:00.000Z",[262,261,394,454],{"path":654,"title":655,"description":656,"date":657,"author":6,"image":658,"readingMinutes":239,"category":202,"project":229,"tags":659,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ftwo-hands-on-one-lever","Two Hands on One Lever","Our deploy failed with a deploy already in progress while the commit it wanted to ship was going live. Anatomy of a benign collision and a trigger safe to lose.","2026-07-23T09:00:00.000Z","\u002Fimages\u002Fblog\u002Ftwo-hands-on-one-lever-hero.jpg",[218,279,660],"observability",{"path":662,"title":663,"description":664,"date":665,"author":6,"image":214,"readingMinutes":239,"category":259,"project":229,"tags":666,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ftwo-hundred-and-fourteen-undecided","Two Hundred and Fourteen Undecided","An accessibility scanner found three faults on the dojo, we fixed them, and the next run came back clean. The clean run was the dangerous one.","2026-08-22T12:00:00.000Z",[646,262,354,233],{"path":668,"title":669,"description":670,"date":671,"author":6,"image":672,"readingMinutes":145,"category":340,"project":229,"tags":673,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Ftwo-validators-one-gate","Two Validators, One Gate","Validating one request body twice, with a Fastify schema and again with Zod, is not double safety. The second gate is unreachable. One validator; Zod for types.","2026-07-07T22:06:46.000Z","\u002Fimages\u002Fblog\u002Ftwo-validators-one-gate-hero.jpg",[354,674,675],"validation","typescript",{"path":677,"title":678,"description":679,"date":680,"author":6,"image":681,"readingMinutes":212,"category":202,"project":229,"tags":682,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fwe-are-all-doing-asynchronous-integration","We Are All Doing Asynchronous Integration","A continuous integration server is not continuous integration. The forge tests your work after you have moved on. Our build takes three minutes; no excuse.","2026-07-09T09:46:00.000Z","\u002Fimages\u002Fblog\u002Fasynchronous-integration-hero.jpg",[232,218,278],{"path":684,"title":685,"description":686,"date":687,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":688,"draft":205,"series":244,"seriesOrder":239},"\u002Fblog\u002Fwe-promised-not-to-watch-then-we-needed-to-see","We Promised Not to Watch. Then We Needed to See.","Our privacy policy said no analytics, and it was true. Adding a page counter meant reopening that promise in public: what we chose, what we refused, one commit.","2026-08-24T10:00:00.000Z",[251,218,689],"analytics",{"path":691,"title":692,"description":693,"date":694,"author":6,"image":695,"readingMinutes":212,"category":202,"project":341,"tags":696,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fwhat-one-real-release-taught-us","What One Real Release Taught Us in an Afternoon","Two crashes and one near miss within minutes of touching the real GitHub, because we had refused to fake it. The race we never met, the merge that never came.","2026-07-21T17:30:00.000Z","\u002Fimages\u002Fblog\u002Fone-real-release-hero.jpg",[403,697,261,346],"failure-modes",{"path":699,"title":700,"description":701,"date":702,"author":6,"image":214,"readingMinutes":212,"category":202,"project":240,"tags":703,"draft":205,"series":244,"seriesOrder":270},"\u002Fblog\u002Fwhat-the-link-looks-like-before-anyone-clicks","What the Link Looks Like Before Anyone Clicks","A link to any page on our site showed up as a bare rectangle of text. The share image is part of the page, and the build now puts one on every route.","2026-08-22T22:00:00.000Z",[242,218,243],{"path":705,"title":706,"description":707,"date":708,"author":6,"image":214,"readingMinutes":212,"category":259,"project":229,"tags":709,"draft":205,"series":455,"seriesOrder":145},"\u002Fblog\u002Fwhat-the-nullable-gave-back","What the Nullable Gave Back","One file, seven behaviours held fixed, the database swapped for a Nullable: about 180 times less time inside the tests, and coverage flat to two decimals.","2026-08-29T09:00:00.000Z",[262,261,394,454],{"path":711,"title":712,"description":713,"date":714,"author":6,"image":214,"readingMinutes":239,"category":202,"project":240,"tags":715,"draft":205,"series":244,"seriesOrder":487},"\u002Fblog\u002Fwhat-we-count-and-what-we-refuse-to-know","What We Count, and What We Refuse to Know","Every system that holds anything about a visitor, in one table in the privacy policy. Writing it found a form that no longer existed and one that wrote twice.","2026-08-23T14:00:00.000Z",[251,218,689],{"path":717,"title":718,"description":719,"date":720,"author":6,"image":721,"readingMinutes":270,"category":340,"project":214,"tags":214,"draft":205,"series":214,"seriesOrder":214},"\u002Fblog\u002Fwhy-good-software-starts-with-the-right-questions","Why Good Software Starts with the Right Questions","Before writing a line of code, the most impactful thing a team can do is ask better questions. Discovery is not a phase to rush. It is the foundation.","2026-01-15T09:00:00.000Z","\u002Fimages\u002Fblog\u002Fright-questions-hero.jpg",1787861096897]