[{"data":1,"prerenderedAt":726},["ShallowReactive",2],{"post-\u002Fblog\u002Fthe-best-coverage-number-in-the-room":3,"blog-all":225},{"id":4,"title":5,"author":6,"body":7,"category":204,"date":205,"description":206,"draft":207,"extension":208,"image":209,"meta":210,"navigation":211,"path":212,"project":213,"readingMinutes":214,"seo":215,"series":216,"seriesOrder":217,"stem":218,"tags":219,"__hash__":224},"blog\u002Fblog\u002Fthe-best-coverage-number-in-the-room.md","The Best Coverage Number in the Room","EkoHacks Team",{"type":8,"value":9,"toc":195},"minimark",[10,14,35,40,121,124,127,131,138,141,144,148,158,161,165,168,171,174,178,181,184],[11,12,13],"p",{},"We have been telling cohorts to stop mocking for two years, which is easy to say and hard to prove. So last winter we started measuring our own codebase instead of asserting things about everyone else's, and we wrote the numbers down as we went, including the ones we did not like.",[11,15,16,17,21,22,25,26,29,30,34],{},"The cleanest measurement is a pair. Two branches sit on the ",[18,19,20],"strong",{},"same production commit",", cover the ",[18,23,24],{},"same behaviour specification",", and run ",[18,27,28],{},"almost the same number of tests",", 71 against 70. One uses ",[31,32,33],"code",{},"vi.mock"," at the collaborator boundary. The other runs sociably against a real database. Nothing else differs. Whatever separates them is the technique and only the technique.",[36,37,39],"h2",{"id":38},"what-came-out","What came out",[41,42,43,60],"table",{},[44,45,46],"thead",{},[47,48,49,53,57],"tr",{},[50,51],"th",{"align":52},"left",[50,54,56],{"align":55},"right","Mocked",[50,58,59],{"align":55},"Sociable",[61,62,63,75,86,97,108],"tbody",{},[47,64,65,69,72],{},[66,67,68],"td",{"align":52},"Tests",[66,70,71],{"align":55},"71",[66,73,74],{"align":55},"70",[47,76,77,80,83],{},[66,78,79],{"align":52},"Wall clock",[66,81,82],{"align":55},"2.29 s",[66,84,85],{"align":55},"12.80 s",[47,87,88,91,94],{},[66,89,90],{"align":52},"Line coverage",[66,92,93],{"align":55},"14.95%",[66,95,96],{"align":55},"18.47%",[47,98,99,102,105],{},[66,100,101],{"align":52},"Function coverage",[66,103,104],{"align":55},"65.95%",[66,106,107],{"align":55},"72.72%",[47,109,110,113,118],{},[66,111,112],{"align":52},"Branch coverage",[66,114,115],{"align":55},[18,116,117],{},"79.16%",[66,119,120],{"align":55},"74.19%",[11,122,123],{},"Read the first three rows and the story is the one you expect. Mocks are 5.6 times faster and execute 3.5 fewer points of the codebase. The mechanism is not subtle. The mocked push and check run tests replace the repository service, the Prisma client and the XP service with stubs. Those functions never run, so they never count. A mock is, by definition, a decision not to execute the thing you are mocking, and a coverage tool is a machine for noticing exactly that.",[11,125,126],{},"Now read the last row again.",[36,128,130],{"id":129},"the-number-that-flatters","The number that flatters",[11,132,133,134,137],{},"The mocked suite posts the ",[18,135,136],{},"highest branch coverage of every condition we measured",". A team reading that off a dashboard would conclude their tests were in excellent health, and they would be badly wrong.",[11,139,140],{},"Branch coverage only measures branches inside code that executes. The mocked suite runs a small, richly branched slice of the system, the parsing, the pure logic, the handler control flow, and it runs that slice very thoroughly indeed. Meanwhile most of the data layer never runs at all, so its branches are not scored as missed, they are simply absent from the question. Restrict the exam to the chapter you revised and your mark goes up.",[11,142,143],{},"This is the part worth taking to your own project. A single high coverage headline can rise as your tests touch less of the system, because the metric measures thoroughness within whatever ran, and mocking is how you shrink what runs. Line and function coverage told the truer story for us. One number on its own told a flattering lie.",[36,145,147],{"id":146},"the-trade-nobody-advertises","The trade nobody advertises",[11,149,150,151,154,155,157],{},"Put the two halves together and the shape is uncomfortable: mocks are much faster ",[18,152,153],{},"because"," they do not run your code, and they cover less ",[18,156,153],{}," they do not run your code. Speed and executed fidelity are not independent dials you can tune separately. For mocks they move together, in opposite directions from the one you want.",[11,159,160],{},"That is the honest case for mocks, incidentally. If a suite exists to give you a fast red or green on pure logic, mocking the world around it is a rational trade. The failure is not choosing speed. The failure is choosing speed and then reading the coverage number as though you had chosen fidelity.",[36,162,164],{"id":163},"what-we-did-about-it","What we did about it",[11,166,167],{},"The Nullable pattern is a claim that you can have both: infrastructure wrapped in a thin class that knows how to build a version of itself with only its lowest level switched off. The database, the clock and the network answer to the test, and every line of your own code between the call and the boundary runs for real.",[11,169,170],{},"We have been converting the dojo to it, commit by commit, with a measurement point at each step. Today's suite is 55 test files, 644 tests, and 95.98% line coverage, against the 35 tests and 9.34% we started with. That is the good half of the sentence.",[11,172,173],{},"The other half: it takes about four minutes. The suite grew slower as it grew truer, which is not the outcome the pattern promises, and we have not yet done the work of separating \"narrow integration tests are inherently slower\" from \"we have been careless about where the database is touched\". Getting it back to seconds without giving back the fidelity is the next thing we measure, and when we have the number, it will go in the notebook whichever way it falls.",[36,175,177],{"id":176},"the-number-for-today","The number for today",[11,179,180],{},"Same code, same specification, same test count: 5.6 times faster, 3.5 points less of the codebase executed, and the best looking branch coverage in the room belonging to the suite that ran the least.",[11,182,183],{},"Next in this series: the twenty six tests we gained on the way out of mocks, and the four behaviours we lost without noticing.",[11,185,186,187,194],{},"We teach this conversion as a four week course, ",[188,189,193],"a",{"href":190,"rel":191},"https:\u002F\u002Fdojo.ekohacks.com\u002Fseats\u002Ftesting-without-mocks",[192],"nofollow","Testing Without Mocks in TypeScript",", two evenings a week, on your own codebase, with the measurements above handed over so you know what it costs before you spend it.",{"title":196,"searchDepth":197,"depth":197,"links":198},"",2,[199,200,201,202,203],{"id":38,"depth":197,"text":39},{"id":129,"depth":197,"text":130},{"id":146,"depth":197,"text":147},{"id":163,"depth":197,"text":164},{"id":176,"depth":197,"text":177},"Testing and TDD","2026-08-27T12:00:00.000Z","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.",false,"md",null,{},true,"\u002Fblog\u002Fthe-best-coverage-number-in-the-room","The Dojo",6,{"title":5,"description":206},"What Mocks Cost",1,"blog\u002Fthe-best-coverage-number-in-the-room",[220,221,222,223],"testing","nullables","mocks","coverage","tTl5Fj2s3N9w9wA0uljR1aytZOtwYxxl3cypJeO-9_g",[226,237,251,259,268,275,284,291,298,307,315,324,331,338,351,360,367,374,383,391,398,408,415,423,430,436,442,451,453,463,471,478,489,497,503,513,522,530,538,546,554,561,569,577,584,590,597,606,614,621,628,637,643,651,657,665,671,680,687,694,702,708,714,720],{"path":227,"title":228,"description":229,"date":230,"author":6,"image":231,"readingMinutes":214,"category":232,"project":213,"tags":233,"draft":207,"series":209,"seriesOrder":209},"\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",[234,235,236],"git","continuous-integration","craft",{"path":238,"title":239,"description":240,"date":241,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":245,"draft":207,"series":249,"seriesOrder":250},"\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,"Shipping and Operations","ekohacks.com",[246,247,248],"seo","operations","nuxt","From Invisible to Findable",3,{"path":252,"title":253,"description":254,"date":255,"author":6,"image":209,"readingMinutes":214,"category":243,"project":244,"tags":256,"draft":207,"series":249,"seriesOrder":258},"\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",[257,247,248],"privacy",9,{"path":260,"title":261,"description":262,"date":263,"author":6,"image":264,"readingMinutes":242,"category":204,"project":265,"tags":266,"draft":207,"series":209,"seriesOrder":209},"\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","EkoLite",[221,220,267],"websocket",{"path":269,"title":270,"description":271,"date":272,"author":6,"image":273,"readingMinutes":274,"category":232,"project":209,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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":276,"title":277,"description":278,"date":279,"author":6,"image":280,"readingMinutes":274,"category":243,"project":213,"tags":281,"draft":207,"series":209,"seriesOrder":209},"\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",[247,282,283],"deployment","idempotency",{"path":285,"title":286,"description":287,"date":288,"author":289,"image":290,"readingMinutes":214,"category":243,"project":209,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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":292,"title":293,"description":294,"date":295,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":296,"draft":207,"series":249,"seriesOrder":297},"\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",[246,247,236],0,{"path":299,"title":300,"description":301,"date":302,"author":6,"image":303,"readingMinutes":274,"category":232,"project":213,"tags":304,"draft":207,"series":209,"seriesOrder":209},"\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",[236,305,306],"fastify","security",{"path":308,"title":309,"description":310,"date":311,"author":6,"image":312,"readingMinutes":313,"category":243,"project":213,"tags":314,"draft":207,"series":209,"seriesOrder":209},"\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,[234,235,247],{"path":316,"title":317,"description":318,"date":319,"author":6,"image":320,"readingMinutes":274,"category":232,"project":213,"tags":321,"draft":207,"series":209,"seriesOrder":209},"\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",[236,322,323],"documentation","ai-agents",{"path":325,"title":326,"description":327,"date":328,"author":6,"image":329,"readingMinutes":214,"category":243,"project":213,"tags":330,"draft":207,"series":209,"seriesOrder":209},"\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",[235,247,220],{"path":332,"title":333,"description":334,"date":335,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":336,"draft":207,"series":249,"seriesOrder":197},"\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",[246,247,248,337],"netlify",{"path":339,"title":340,"description":341,"date":342,"author":6,"image":343,"readingMinutes":274,"category":344,"project":345,"tags":346,"draft":207,"series":209,"seriesOrder":209},"\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",[347,348,349,350],"composition","cli-design","narration","encoding-the-release",{"path":352,"title":353,"description":354,"date":355,"author":6,"image":356,"readingMinutes":242,"category":344,"project":265,"tags":357,"draft":207,"series":209,"seriesOrder":209},"\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",[358,221,359],"design","error handling",{"path":361,"title":362,"description":363,"date":364,"author":6,"image":365,"readingMinutes":214,"category":243,"project":213,"tags":366,"draft":207,"series":209,"seriesOrder":209},"\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",[235,282,247],{"path":368,"title":369,"description":370,"date":371,"author":6,"image":372,"readingMinutes":214,"category":232,"project":213,"tags":373,"draft":207,"series":209,"seriesOrder":209},"\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",[234,235,236],{"path":375,"title":376,"description":377,"date":378,"author":6,"image":379,"readingMinutes":250,"category":344,"project":213,"tags":380,"draft":207,"series":209,"seriesOrder":209},"\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",[358,381,382],"data","onboarding",{"path":384,"title":385,"description":386,"date":387,"author":6,"image":209,"readingMinutes":214,"category":204,"project":345,"tags":388,"draft":207,"series":209,"seriesOrder":209},"\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",[389,221,348,390],"user-testing","linear",{"path":392,"title":393,"description":394,"date":395,"author":6,"image":396,"readingMinutes":313,"category":204,"project":213,"tags":397,"draft":207,"series":209,"seriesOrder":209},"\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",[220,221,222],{"path":399,"title":400,"description":401,"date":402,"author":6,"image":403,"readingMinutes":274,"category":243,"project":345,"tags":404,"draft":207,"series":209,"seriesOrder":209},"\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",[405,406,407,350],"automation","releasing","process",{"path":409,"title":410,"description":411,"date":378,"author":6,"image":412,"readingMinutes":250,"category":243,"project":213,"tags":413,"draft":207,"series":209,"seriesOrder":209},"\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",[247,283,414],"webhooks",{"path":416,"title":417,"description":418,"date":419,"author":6,"image":209,"readingMinutes":214,"category":243,"project":213,"tags":420,"draft":207,"series":209,"seriesOrder":209},"\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",[421,422,347,247],"shell","provisioning",{"path":424,"title":425,"description":426,"date":209,"author":427,"image":428,"readingMinutes":217,"category":344,"project":429,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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":431,"title":432,"description":433,"date":434,"author":6,"image":209,"readingMinutes":242,"category":204,"project":244,"tags":435,"draft":207,"series":249,"seriesOrder":313},"\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",[246,220,248],{"path":437,"title":438,"description":439,"date":440,"author":6,"image":441,"readingMinutes":197,"category":204,"project":209,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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":443,"title":444,"description":445,"date":446,"author":6,"image":447,"readingMinutes":313,"category":204,"project":345,"tags":448,"draft":207,"series":209,"seriesOrder":209},"\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",[221,449,450,350],"testing-without-mocks","james-shore",{"path":212,"title":5,"description":206,"date":205,"author":6,"image":209,"readingMinutes":214,"category":204,"project":213,"tags":452,"draft":207,"series":216,"seriesOrder":217},[220,221,222,223],{"path":454,"title":455,"description":456,"date":457,"author":6,"image":458,"readingMinutes":313,"category":344,"project":265,"tags":459,"draft":207,"series":209,"seriesOrder":209},"\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",[460,461,220,462],"protocol","pubsub","tdd",{"path":464,"title":465,"description":466,"date":467,"author":6,"image":468,"readingMinutes":214,"category":204,"project":265,"tags":469,"draft":207,"series":209,"seriesOrder":209},"\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",[221,220,470],"refactoring",{"path":472,"title":473,"description":474,"date":475,"author":6,"image":476,"readingMinutes":313,"category":232,"project":213,"tags":477,"draft":207,"series":209,"seriesOrder":209},"\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",[234,235,236],{"path":479,"title":480,"description":481,"date":482,"author":6,"image":483,"readingMinutes":484,"category":243,"project":213,"tags":485,"draft":207,"series":209,"seriesOrder":209},"\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,[247,486,487,488],"debugging","european-tech","community",{"path":490,"title":491,"description":492,"date":493,"author":6,"image":494,"readingMinutes":214,"category":344,"project":265,"tags":495,"draft":207,"series":209,"seriesOrder":209},"\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",[358,462,496],"continuous integration",{"path":498,"title":499,"description":500,"date":501,"author":6,"image":502,"readingMinutes":274,"category":232,"project":209,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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":504,"title":505,"description":506,"date":507,"author":6,"image":508,"readingMinutes":242,"category":232,"project":213,"tags":509,"draft":207,"series":209,"seriesOrder":209},"\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",[510,511,512,390],"graphql","stories","xp",{"path":514,"title":515,"description":516,"date":517,"author":6,"image":518,"readingMinutes":313,"category":204,"project":345,"tags":519,"draft":207,"series":209,"seriesOrder":209},"\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",[462,520,521,350],"red-first","code-review",{"path":523,"title":524,"description":525,"date":526,"author":6,"image":527,"readingMinutes":313,"category":243,"project":345,"tags":528,"draft":207,"series":209,"seriesOrder":209},"\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",[406,529,234,350],"preflight",{"path":531,"title":532,"description":533,"date":534,"author":6,"image":535,"readingMinutes":313,"category":243,"project":265,"tags":536,"draft":207,"series":209,"seriesOrder":209},"\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",[537,221,220],"shutdown",{"path":539,"title":540,"description":541,"date":542,"author":6,"image":543,"readingMinutes":214,"category":243,"project":265,"tags":544,"draft":207,"series":209,"seriesOrder":209},"\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",[545,220,236],"packaging",{"path":547,"title":548,"description":549,"date":550,"author":6,"image":551,"readingMinutes":274,"category":344,"project":345,"tags":552,"draft":207,"series":209,"seriesOrder":209},"\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",[405,553,358,350],"human-in-the-loop",{"path":555,"title":556,"description":557,"date":558,"author":6,"image":559,"readingMinutes":214,"category":243,"project":213,"tags":560,"draft":207,"series":209,"seriesOrder":209},"\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",[235,247,236],{"path":562,"title":563,"description":564,"date":565,"author":6,"image":566,"readingMinutes":214,"category":243,"project":265,"tags":567,"draft":207,"series":209,"seriesOrder":209},"\u002Fblog\u002Fthe-knock-and-the-axe","The Knock and the Axe","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.","2026-07-20T12:00:00.000Z","\u002Fimages\u002Fblog\u002Fthe-knock-and-the-axe-hero.jpg",[537,247,568],"signals",{"path":570,"title":571,"description":572,"date":573,"author":6,"image":574,"readingMinutes":484,"category":232,"project":265,"tags":575,"draft":207,"series":209,"seriesOrder":209},"\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",[521,470,576,220],"teaching",{"path":578,"title":579,"description":580,"date":581,"author":6,"image":582,"readingMinutes":214,"category":344,"project":265,"tags":583,"draft":207,"series":209,"seriesOrder":209},"\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",[358,461,221],{"path":585,"title":586,"description":587,"date":588,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":589,"draft":207,"series":249,"seriesOrder":217},"\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",[246,247,248],{"path":591,"title":592,"description":593,"date":594,"author":6,"image":595,"readingMinutes":484,"category":243,"project":213,"tags":596,"draft":207,"series":209,"seriesOrder":209},"\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",[247,486,487,488],{"path":598,"title":599,"description":600,"date":601,"author":6,"image":602,"readingMinutes":274,"category":232,"project":345,"tags":603,"draft":211,"series":209,"seriesOrder":209},"\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",[406,604,605,350],"dogfooding","acceptance-testing",{"path":607,"title":608,"description":609,"date":610,"author":6,"image":611,"readingMinutes":242,"category":204,"project":265,"tags":612,"draft":207,"series":209,"seriesOrder":209},"\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",[220,221,613],"scriptrunner",{"path":615,"title":616,"description":617,"date":618,"author":6,"image":209,"readingMinutes":484,"category":243,"project":244,"tags":619,"draft":207,"series":249,"seriesOrder":214},"\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",[246,247,620],"performance",{"path":622,"title":623,"description":624,"date":625,"author":6,"image":626,"readingMinutes":242,"category":204,"project":265,"tags":627,"draft":207,"series":209,"seriesOrder":209},"\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",[220,221,267],{"path":629,"title":630,"description":631,"date":632,"author":427,"image":633,"readingMinutes":214,"category":232,"project":634,"tags":635,"draft":207,"series":209,"seriesOrder":209},"\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",[236,636,381,576],"content",{"path":638,"title":639,"description":640,"date":457,"author":6,"image":641,"readingMinutes":313,"category":204,"project":265,"tags":642,"draft":207,"series":209,"seriesOrder":209},"\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",[221,220,236,576],{"path":644,"title":645,"description":646,"date":632,"author":427,"image":647,"readingMinutes":274,"category":232,"project":634,"tags":648,"draft":207,"series":209,"seriesOrder":209},"\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",[649,234,576,650],"workflow","accessibility",{"path":652,"title":653,"description":654,"date":655,"author":6,"image":209,"readingMinutes":214,"category":204,"project":213,"tags":656,"draft":207,"series":216,"seriesOrder":197},"\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",[220,221,222,223],{"path":658,"title":659,"description":660,"date":661,"author":6,"image":662,"readingMinutes":242,"category":243,"project":213,"tags":663,"draft":207,"series":209,"seriesOrder":209},"\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",[247,283,664],"observability",{"path":666,"title":667,"description":668,"date":669,"author":6,"image":209,"readingMinutes":242,"category":204,"project":213,"tags":670,"draft":207,"series":209,"seriesOrder":209},"\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",[650,220,358,236],{"path":672,"title":673,"description":674,"date":675,"author":6,"image":676,"readingMinutes":250,"category":344,"project":213,"tags":677,"draft":207,"series":209,"seriesOrder":209},"\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",[358,678,679],"validation","typescript",{"path":681,"title":682,"description":683,"date":684,"author":6,"image":685,"readingMinutes":214,"category":243,"project":213,"tags":686,"draft":207,"series":209,"seriesOrder":209},"\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",[235,247,282],{"path":688,"title":689,"description":690,"date":691,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":692,"draft":207,"series":249,"seriesOrder":242},"\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",[257,247,693],"analytics",{"path":695,"title":696,"description":697,"date":698,"author":6,"image":699,"readingMinutes":214,"category":243,"project":345,"tags":700,"draft":207,"series":209,"seriesOrder":209},"\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",[406,701,221,350],"failure-modes",{"path":703,"title":704,"description":705,"date":706,"author":6,"image":209,"readingMinutes":214,"category":243,"project":244,"tags":707,"draft":207,"series":249,"seriesOrder":274},"\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",[246,247,248],{"path":709,"title":710,"description":711,"date":712,"author":6,"image":209,"readingMinutes":214,"category":204,"project":213,"tags":713,"draft":207,"series":216,"seriesOrder":250},"\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",[220,221,222,223],{"path":715,"title":716,"description":717,"date":718,"author":6,"image":209,"readingMinutes":242,"category":243,"project":244,"tags":719,"draft":207,"series":249,"seriesOrder":484},"\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",[257,247,693],{"path":721,"title":722,"description":723,"date":724,"author":6,"image":725,"readingMinutes":274,"category":344,"project":209,"tags":209,"draft":207,"series":209,"seriesOrder":209},"\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",1787861096792]