[{"data":1,"prerenderedAt":833},["ShallowReactive",2],{"post-\u002Fblog\u002Fintegrate-against-the-trunk":3,"blog-all":333},{"id":4,"title":5,"author":6,"body":7,"category":315,"date":316,"description":317,"draft":318,"extension":319,"image":320,"meta":321,"navigation":322,"path":323,"project":324,"readingMinutes":325,"seo":326,"series":327,"seriesOrder":327,"stem":328,"tags":329,"__hash__":332},"blog\u002Fblog\u002Fintegrate-against-the-trunk.md","Integrate Against the Trunk, Not Your Copy of It","EkoHacks Team",{"type":8,"value":9,"toc":308},"minimark",[10,20,57,68,71,76,81,95,104,114,118,124,127,133,137,144,152,164,175,179,182,185,227,233,236,264,268,276,279,288,291,294,304],[11,12,13,14,19],"p",{},"When we untangled ",[15,16,18],"a",{"href":17},"\u002Fblog\u002Fthe-conflict-nobody-wrote","the conflict nobody wrote",", the fix came down to one instruction: put the branch on top of the current trunk and regenerate. Written out, it read like this.",[21,22,27],"pre",{"className":23,"code":24,"language":25,"meta":26,"style":26},"language-bash shiki shiki-themes github-dark","git fetch origin\ngit rebase origin\u002Fmain\n","bash","",[28,29,30,46],"code",{"__ignoreMap":26},[31,32,35,39,43],"span",{"class":33,"line":34},"line",1,[31,36,38],{"class":37},"svObZ","git",[31,40,42],{"class":41},"sU2Wk"," fetch",[31,44,45],{"class":41}," origin\n",[31,47,49,51,54],{"class":33,"line":48},2,[31,50,38],{"class":37},[31,52,53],{"class":41}," rebase",[31,55,56],{"class":41}," origin\u002Fmain\n",[11,58,59,60,63,64,67],{},"A fair question came back. Why ",[28,61,62],{},"origin\u002Fmain",", when there is a perfectly good ",[28,65,66],{},"main"," sitting right there in the clone? If the trunk has already been pulled in, can the rebase not use the local one?",[11,69,70],{},"It can. The answer is yes, and the yes has a condition attached that is worth more than the answer.",[72,73,75],"h2",{"id":74},"two-names-and-only-one-of-them-is-the-trunk","Two names, and only one of them is the trunk",[11,77,78,80],{},[28,79,66],{}," is a branch in your repository. It is a file containing a commit id, and it moves only when you move it, by committing, merging, pulling, or resetting.",[11,82,83,85,86,90,91,94],{},[28,84,62],{}," is a ",[87,88,89],"strong",{},"remote tracking reference",". It is also a file containing a commit id, and it moves only when you run ",[28,92,93],{},"git fetch",". What it holds is not what the remote has. It is what the remote had the last time you asked.",[11,96,97,98,100,101,103],{},"So there are three versions of the trunk in play at any moment, and it is easy to believe there is one. There is the trunk on the server, which is the real one, the one everybody else is integrating with and the one the forge uses to decide whether your pull request can merge. There is ",[28,99,62],{}," in your clone, a snapshot of the server taken at your last fetch. And there is ",[28,102,66],{}," in your clone, which is a branch you happen to have given the same name as the trunk, and which git treats as no more authoritative than any other branch you have made.",[11,105,106,109,110,113],{},[28,107,108],{},"git rebase main"," and ",[28,111,112],{},"git rebase origin\u002Fmain"," are identical commands whenever those two names resolve to the same commit. When they do not, one of them is integration and the other is a rehearsal.",[72,115,117],{"id":116},"the-failure-is-silent-which-is-the-problem","The failure is silent, which is the problem",[11,119,120,121,123],{},"Suppose your local ",[28,122,66],{}," is two days old. You rebase onto it. The rebase runs, you resolve the conflict thoughtfully, the tests pass, you push, and the pull request still says conflicting.",[11,125,126],{},"Nothing warned you. The rebase did not fail. It could not fail, because you asked it to replay your work on top of a commit and it did precisely that. You integrated with a version of the trunk that exists nowhere but your disk, and every minute you spent resolving that conflict was spent answering a question nobody had asked.",[11,128,129,130,132],{},"There is a second, worse shape. If your local ",[28,131,66],{}," carries commits you have not pushed, perhaps something you committed there weeks ago and forgot, rebasing onto it slides those commits underneath your branch. The pull request now contains work unrelated to the change it claims to make, and the reviewer, reading a diff about a quota, finds a stray refactor in it.",[72,134,136],{"id":135},"the-trap-that-makes-it-convincing","The trap that makes it convincing",[11,138,139,140,143],{},"Here is the part that catches careful people. Run ",[28,141,142],{},"git status"," on a stale clone and it will tell you, with total confidence:",[21,145,150],{"className":146,"code":148,"language":149},[147],"language-text","On branch main\nYour branch is up to date with 'origin\u002Fmain'.\n","text",[28,151,148],{"__ignoreMap":26},[11,153,154,155,157,158,160,161,163],{},"That sentence is true and it does not mean what it appears to mean. Git is comparing your ",[28,156,66],{}," against your ",[28,159,62],{},", both of which are local files. It is telling you that your copy agrees with your copy. It has not spoken to the server, because ",[28,162,142],{}," never speaks to the server. Two days of other people's work can sit on the trunk while your clone insists everything is current.",[11,165,166,167,170,171,174],{},"The same applies to ",[28,168,169],{},"git log origin\u002Fmain",", to the ahead and behind counts in your editor's status bar, and to every other reading of the world that has not been preceded by a fetch. ",[87,172,173],{},"Nothing in git reaches across the network unless you ask it to."," The remote tracking reference is a cache, and, exactly as we found with the generated document in the previous post, a cache tells you what was true when it was written.",[72,176,178],{"id":177},"the-practice-underneath","The practice underneath",[11,180,181],{},"The old discipline for integrating has two steps and people usually remember only the second. Before you put your work into the repository, you bring the repository's work into yours, and you prove that the combination builds and passes its tests. The first step is not \"update your local main\". It is \"get what everybody else has\".",[11,183,184],{},"So the shape of an honest integration is:",[21,186,188],{"className":23,"code":187,"language":25,"meta":26,"style":26},"git fetch origin              # go and actually look\ngit rebase origin\u002Fmain        # integrate with what is there\nnpm test                      # prove the combination works\n",[28,189,190,203,215],{"__ignoreMap":26},[31,191,192,194,196,199],{"class":33,"line":34},[31,193,38],{"class":37},[31,195,42],{"class":41},[31,197,198],{"class":41}," origin",[31,200,202],{"class":201},"sAwPA","              # go and actually look\n",[31,204,205,207,209,212],{"class":33,"line":48},[31,206,38],{"class":37},[31,208,53],{"class":41},[31,210,211],{"class":41}," origin\u002Fmain",[31,213,214],{"class":201},"        # integrate with what is there\n",[31,216,218,221,224],{"class":33,"line":217},3,[31,219,220],{"class":37},"npm",[31,222,223],{"class":41}," test",[31,225,226],{"class":201},"                      # prove the combination works\n",[11,228,229,230,232],{},"The fetch is the only line that touches the network, and it is the only line that turns a private opinion about the trunk into a fact about it. If you prefer to work through a local ",[28,231,66],{},", fast forward it first and then use it. The name you type afterwards is a matter of taste. Having fetched is not.",[11,234,235],{},"Two commands settle the question when you are unsure:",[21,237,239],{"className":23,"code":238,"language":25,"meta":26,"style":26},"git fetch origin\ngit rev-parse main origin\u002Fmain   # same commit id twice? then either name works\n",[28,240,241,249],{"__ignoreMap":26},[31,242,243,245,247],{"class":33,"line":34},[31,244,38],{"class":37},[31,246,42],{"class":41},[31,248,45],{"class":41},[31,250,251,253,256,259,261],{"class":33,"line":48},[31,252,38],{"class":37},[31,254,255],{"class":41}," rev-parse",[31,257,258],{"class":41}," main",[31,260,211],{"class":41},[31,262,263],{"class":201},"   # same commit id twice? then either name works\n",[72,265,267],{"id":266},"why-the-difference-is-the-point","Why the difference is the point",[11,269,270,271,109,273,275],{},"It would be easy to file this under command line trivia. It is not, and the reason is that the gap between ",[28,272,66],{},[28,274,62],{}," is a measurement.",[11,277,278],{},"If those two references have drifted apart, you are looking at work that other people have finished and you have not yet reckoned with. That is the definition of being unintegrated. The size of the gap is the size of the surprise waiting for you, and the only thing that shrinks it is fetching more often and integrating more often.",[11,280,281,282,284,285,287],{},"Which means the question \"should I use ",[28,283,66],{}," or ",[28,286,62],{},"?\" answers itself under a discipline of continuous integration. A team that brings the trunk into their work every few hours will find the two names pointing at the same commit almost every time they look, and the distinction will feel academic. A team that discovers a real difference between them has not found a naming subtlety. They have found out how far behind they are.",[11,289,290],{},"Our own conflict came from a branch that was one merge behind the trunk. One. That is how little divergence it takes, and it is the subject of the next two posts: what a branch costs while you are not looking at it, and why the argument about how to catch up is less interesting than the fact that you had to.",[292,293],"hr",{},[11,295,296,300,301],{},[297,298,299],"em",{},"The practice of continuous integration described in this series is set out in the continuous integration chapter of"," The Art of Agile Development ",[297,302,303],{},"by James Shore and Shane Warden.",[305,306,307],"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 .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);}html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}",{"title":26,"searchDepth":48,"depth":48,"links":309},[310,311,312,313,314],{"id":74,"depth":48,"text":75},{"id":116,"depth":48,"text":117},{"id":135,"depth":48,"text":136},{"id":177,"depth":48,"text":178},{"id":266,"depth":48,"text":267},"Shipping and Operations","2026-07-09T09:22:00.000Z","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.",false,"md","\u002Fimages\u002Fblog\u002Fintegrate-against-the-trunk-hero.jpg",{},true,"\u002Fblog\u002Fintegrate-against-the-trunk","The Dojo",5,{"title":5,"description":317},null,"blog\u002Fintegrate-against-the-trunk",[38,330,331],"continuous-integration","operations","rokZRHd_U-7CYjmssFlN9hdxEgr5wkLyi4J6c1bogkI",[334,344,355,363,375,382,391,398,405,414,416,425,432,439,452,461,468,475,484,492,500,510,517,525,532,538,544,553,561,571,579,585,596,604,610,620,629,637,645,653,661,668,676,684,691,697,704,713,721,728,735,744,750,758,764,772,778,787,794,801,809,815,821,827],{"path":335,"title":336,"description":337,"date":338,"author":6,"image":339,"readingMinutes":340,"category":341,"project":324,"tags":342,"draft":318,"series":327,"seriesOrder":327},"\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",6,"Craft and Practice",[38,330,343],"craft",{"path":345,"title":346,"description":347,"date":348,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":351,"draft":318,"series":354,"seriesOrder":217},"\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",[352,331,353],"seo","nuxt","From Invisible to Findable",{"path":356,"title":357,"description":358,"date":359,"author":6,"image":327,"readingMinutes":340,"category":315,"project":350,"tags":360,"draft":318,"series":354,"seriesOrder":362},"\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",[361,331,353],"privacy",9,{"path":364,"title":365,"description":366,"date":367,"author":6,"image":368,"readingMinutes":349,"category":369,"project":370,"tags":371,"draft":318,"series":327,"seriesOrder":327},"\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","EkoLite",[372,373,374],"nullables","testing","websocket",{"path":376,"title":377,"description":378,"date":379,"author":6,"image":380,"readingMinutes":381,"category":341,"project":327,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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":383,"title":384,"description":385,"date":386,"author":6,"image":387,"readingMinutes":381,"category":315,"project":324,"tags":388,"draft":318,"series":327,"seriesOrder":327},"\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",[331,389,390],"deployment","idempotency",{"path":392,"title":393,"description":394,"date":395,"author":396,"image":397,"readingMinutes":340,"category":315,"project":327,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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":399,"title":400,"description":401,"date":402,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":403,"draft":318,"series":354,"seriesOrder":404},"\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",[352,331,343],0,{"path":406,"title":407,"description":408,"date":409,"author":6,"image":410,"readingMinutes":381,"category":341,"project":324,"tags":411,"draft":318,"series":327,"seriesOrder":327},"\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",[343,412,413],"fastify","security",{"path":323,"title":5,"description":317,"date":316,"author":6,"image":320,"readingMinutes":325,"category":315,"project":324,"tags":415,"draft":318,"series":327,"seriesOrder":327},[38,330,331],{"path":417,"title":418,"description":419,"date":420,"author":6,"image":421,"readingMinutes":381,"category":341,"project":324,"tags":422,"draft":318,"series":327,"seriesOrder":327},"\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",[343,423,424],"documentation","ai-agents",{"path":426,"title":427,"description":428,"date":429,"author":6,"image":430,"readingMinutes":340,"category":315,"project":324,"tags":431,"draft":318,"series":327,"seriesOrder":327},"\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",[330,331,373],{"path":433,"title":434,"description":435,"date":436,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":437,"draft":318,"series":354,"seriesOrder":48},"\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",[352,331,353,438],"netlify",{"path":440,"title":441,"description":442,"date":443,"author":6,"image":444,"readingMinutes":381,"category":445,"project":446,"tags":447,"draft":318,"series":327,"seriesOrder":327},"\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",[448,449,450,451],"composition","cli-design","narration","encoding-the-release",{"path":453,"title":454,"description":455,"date":456,"author":6,"image":457,"readingMinutes":349,"category":445,"project":370,"tags":458,"draft":318,"series":327,"seriesOrder":327},"\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",[459,372,460],"design","error handling",{"path":462,"title":463,"description":464,"date":465,"author":6,"image":466,"readingMinutes":340,"category":315,"project":324,"tags":467,"draft":318,"series":327,"seriesOrder":327},"\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",[330,389,331],{"path":469,"title":470,"description":471,"date":472,"author":6,"image":473,"readingMinutes":340,"category":341,"project":324,"tags":474,"draft":318,"series":327,"seriesOrder":327},"\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",[38,330,343],{"path":476,"title":477,"description":478,"date":479,"author":6,"image":480,"readingMinutes":217,"category":445,"project":324,"tags":481,"draft":318,"series":327,"seriesOrder":327},"\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",[459,482,483],"data","onboarding",{"path":485,"title":486,"description":487,"date":488,"author":6,"image":327,"readingMinutes":340,"category":369,"project":446,"tags":489,"draft":318,"series":327,"seriesOrder":327},"\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",[490,372,449,491],"user-testing","linear",{"path":493,"title":494,"description":495,"date":496,"author":6,"image":497,"readingMinutes":325,"category":369,"project":324,"tags":498,"draft":318,"series":327,"seriesOrder":327},"\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",[373,372,499],"mocks",{"path":501,"title":502,"description":503,"date":504,"author":6,"image":505,"readingMinutes":381,"category":315,"project":446,"tags":506,"draft":318,"series":327,"seriesOrder":327},"\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",[507,508,509,451],"automation","releasing","process",{"path":511,"title":512,"description":513,"date":479,"author":6,"image":514,"readingMinutes":217,"category":315,"project":324,"tags":515,"draft":318,"series":327,"seriesOrder":327},"\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",[331,390,516],"webhooks",{"path":518,"title":519,"description":520,"date":521,"author":6,"image":327,"readingMinutes":340,"category":315,"project":324,"tags":522,"draft":318,"series":327,"seriesOrder":327},"\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",[523,524,448,331],"shell","provisioning",{"path":526,"title":527,"description":528,"date":327,"author":529,"image":530,"readingMinutes":34,"category":445,"project":531,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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":533,"title":534,"description":535,"date":536,"author":6,"image":327,"readingMinutes":349,"category":369,"project":350,"tags":537,"draft":318,"series":354,"seriesOrder":325},"\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",[352,373,353],{"path":539,"title":540,"description":541,"date":542,"author":6,"image":543,"readingMinutes":48,"category":369,"project":327,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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":545,"title":546,"description":547,"date":548,"author":6,"image":549,"readingMinutes":325,"category":369,"project":446,"tags":550,"draft":318,"series":327,"seriesOrder":327},"\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",[372,551,552,451],"testing-without-mocks","james-shore",{"path":554,"title":555,"description":556,"date":557,"author":6,"image":327,"readingMinutes":340,"category":369,"project":324,"tags":558,"draft":318,"series":560,"seriesOrder":34},"\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",[373,372,499,559],"coverage","What Mocks Cost",{"path":562,"title":563,"description":564,"date":565,"author":6,"image":566,"readingMinutes":325,"category":445,"project":370,"tags":567,"draft":318,"series":327,"seriesOrder":327},"\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",[568,569,373,570],"protocol","pubsub","tdd",{"path":572,"title":573,"description":574,"date":575,"author":6,"image":576,"readingMinutes":340,"category":369,"project":370,"tags":577,"draft":318,"series":327,"seriesOrder":327},"\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",[372,373,578],"refactoring",{"path":17,"title":580,"description":581,"date":582,"author":6,"image":583,"readingMinutes":325,"category":341,"project":324,"tags":584,"draft":318,"series":327,"seriesOrder":327},"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",[38,330,343],{"path":586,"title":587,"description":588,"date":589,"author":6,"image":590,"readingMinutes":591,"category":315,"project":324,"tags":592,"draft":318,"series":327,"seriesOrder":327},"\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,[331,593,594,595],"debugging","european-tech","community",{"path":597,"title":598,"description":599,"date":600,"author":6,"image":601,"readingMinutes":340,"category":445,"project":370,"tags":602,"draft":318,"series":327,"seriesOrder":327},"\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",[459,570,603],"continuous integration",{"path":605,"title":606,"description":607,"date":608,"author":6,"image":609,"readingMinutes":381,"category":341,"project":327,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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":611,"title":612,"description":613,"date":614,"author":6,"image":615,"readingMinutes":349,"category":341,"project":324,"tags":616,"draft":318,"series":327,"seriesOrder":327},"\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",[617,618,619,491],"graphql","stories","xp",{"path":621,"title":622,"description":623,"date":624,"author":6,"image":625,"readingMinutes":325,"category":369,"project":446,"tags":626,"draft":318,"series":327,"seriesOrder":327},"\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",[570,627,628,451],"red-first","code-review",{"path":630,"title":631,"description":632,"date":633,"author":6,"image":634,"readingMinutes":325,"category":315,"project":446,"tags":635,"draft":318,"series":327,"seriesOrder":327},"\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",[508,636,38,451],"preflight",{"path":638,"title":639,"description":640,"date":641,"author":6,"image":642,"readingMinutes":325,"category":315,"project":370,"tags":643,"draft":318,"series":327,"seriesOrder":327},"\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",[644,372,373],"shutdown",{"path":646,"title":647,"description":648,"date":649,"author":6,"image":650,"readingMinutes":340,"category":315,"project":370,"tags":651,"draft":318,"series":327,"seriesOrder":327},"\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",[652,373,343],"packaging",{"path":654,"title":655,"description":656,"date":657,"author":6,"image":658,"readingMinutes":381,"category":445,"project":446,"tags":659,"draft":318,"series":327,"seriesOrder":327},"\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",[507,660,459,451],"human-in-the-loop",{"path":662,"title":663,"description":664,"date":665,"author":6,"image":666,"readingMinutes":340,"category":315,"project":324,"tags":667,"draft":318,"series":327,"seriesOrder":327},"\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",[330,331,343],{"path":669,"title":670,"description":671,"date":672,"author":6,"image":673,"readingMinutes":340,"category":315,"project":370,"tags":674,"draft":318,"series":327,"seriesOrder":327},"\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",[644,331,675],"signals",{"path":677,"title":678,"description":679,"date":680,"author":6,"image":681,"readingMinutes":591,"category":341,"project":370,"tags":682,"draft":318,"series":327,"seriesOrder":327},"\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",[628,578,683,373],"teaching",{"path":685,"title":686,"description":687,"date":688,"author":6,"image":689,"readingMinutes":340,"category":445,"project":370,"tags":690,"draft":318,"series":327,"seriesOrder":327},"\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",[459,569,372],{"path":692,"title":693,"description":694,"date":695,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":696,"draft":318,"series":354,"seriesOrder":34},"\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",[352,331,353],{"path":698,"title":699,"description":700,"date":701,"author":6,"image":702,"readingMinutes":591,"category":315,"project":324,"tags":703,"draft":318,"series":327,"seriesOrder":327},"\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",[331,593,594,595],{"path":705,"title":706,"description":707,"date":708,"author":6,"image":709,"readingMinutes":381,"category":341,"project":446,"tags":710,"draft":322,"series":327,"seriesOrder":327},"\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",[508,711,712,451],"dogfooding","acceptance-testing",{"path":714,"title":715,"description":716,"date":717,"author":6,"image":718,"readingMinutes":349,"category":369,"project":370,"tags":719,"draft":318,"series":327,"seriesOrder":327},"\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",[373,372,720],"scriptrunner",{"path":722,"title":723,"description":724,"date":725,"author":6,"image":327,"readingMinutes":591,"category":315,"project":350,"tags":726,"draft":318,"series":354,"seriesOrder":340},"\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",[352,331,727],"performance",{"path":729,"title":730,"description":731,"date":732,"author":6,"image":733,"readingMinutes":349,"category":369,"project":370,"tags":734,"draft":318,"series":327,"seriesOrder":327},"\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",[373,372,374],{"path":736,"title":737,"description":738,"date":739,"author":529,"image":740,"readingMinutes":340,"category":341,"project":741,"tags":742,"draft":318,"series":327,"seriesOrder":327},"\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",[343,743,482,683],"content",{"path":745,"title":746,"description":747,"date":565,"author":6,"image":748,"readingMinutes":325,"category":369,"project":370,"tags":749,"draft":318,"series":327,"seriesOrder":327},"\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",[372,373,343,683],{"path":751,"title":752,"description":753,"date":739,"author":529,"image":754,"readingMinutes":381,"category":341,"project":741,"tags":755,"draft":318,"series":327,"seriesOrder":327},"\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",[756,38,683,757],"workflow","accessibility",{"path":759,"title":760,"description":761,"date":762,"author":6,"image":327,"readingMinutes":340,"category":369,"project":324,"tags":763,"draft":318,"series":560,"seriesOrder":48},"\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",[373,372,499,559],{"path":765,"title":766,"description":767,"date":768,"author":6,"image":769,"readingMinutes":349,"category":315,"project":324,"tags":770,"draft":318,"series":327,"seriesOrder":327},"\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",[331,390,771],"observability",{"path":773,"title":774,"description":775,"date":776,"author":6,"image":327,"readingMinutes":349,"category":369,"project":324,"tags":777,"draft":318,"series":327,"seriesOrder":327},"\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",[757,373,459,343],{"path":779,"title":780,"description":781,"date":782,"author":6,"image":783,"readingMinutes":217,"category":445,"project":324,"tags":784,"draft":318,"series":327,"seriesOrder":327},"\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",[459,785,786],"validation","typescript",{"path":788,"title":789,"description":790,"date":791,"author":6,"image":792,"readingMinutes":340,"category":315,"project":324,"tags":793,"draft":318,"series":327,"seriesOrder":327},"\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",[330,331,389],{"path":795,"title":796,"description":797,"date":798,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":799,"draft":318,"series":354,"seriesOrder":349},"\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",[361,331,800],"analytics",{"path":802,"title":803,"description":804,"date":805,"author":6,"image":806,"readingMinutes":340,"category":315,"project":446,"tags":807,"draft":318,"series":327,"seriesOrder":327},"\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",[508,808,372,451],"failure-modes",{"path":810,"title":811,"description":812,"date":813,"author":6,"image":327,"readingMinutes":340,"category":315,"project":350,"tags":814,"draft":318,"series":354,"seriesOrder":381},"\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",[352,331,353],{"path":816,"title":817,"description":818,"date":819,"author":6,"image":327,"readingMinutes":340,"category":369,"project":324,"tags":820,"draft":318,"series":560,"seriesOrder":217},"\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",[373,372,499,559],{"path":822,"title":823,"description":824,"date":825,"author":6,"image":327,"readingMinutes":349,"category":315,"project":350,"tags":826,"draft":318,"series":354,"seriesOrder":591},"\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",[361,331,800],{"path":828,"title":829,"description":830,"date":831,"author":6,"image":832,"readingMinutes":381,"category":445,"project":327,"tags":327,"draft":318,"series":327,"seriesOrder":327},"\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",1787861096089]