<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>dependency injection on The Joko Engineering Blog</title>
    <link>/tags/dependency-injection/</link>
    <description>Recent content in dependency injection on The Joko Engineering Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Wed, 26 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/dependency-injection/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Clean Architecture at Joko, or How to Make a Codebase Someone Else Can Change</title>
      <link>/posts/clean-architecture-at-joko-or-how-to-make-a-codebase-someone-else-can-change/</link>
      <pubDate>Wed, 26 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/clean-architecture-at-joko-or-how-to-make-a-codebase-someone-else-can-change/</guid>
      <description>Every codebase starts clean. The tangle arrives quietly, one reasonable shortcut at a time: a database call slipped into a pricing function, an environment variable read three layers deep, a test that needs a running container because there&amp;rsquo;s no other way to reach the code.
At Joko we&amp;rsquo;re building Juno, an AI shopping assistant, on a platform that ingests millions of product offers a day and keeps evolving under full production load.</description>
    </item>
    
  </channel>
</rss>
