<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Gikaru on Medium]]></title>
        <description><![CDATA[Stories by Michael Gikaru on Medium]]></description>
        <link>https://medium.com/@thealmikey?source=rss-283d4a1eeb7e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NvJ5OdziQ2J2n8z6UV7MxQ.jpeg</url>
            <title>Stories by Michael Gikaru on Medium</title>
            <link>https://medium.com/@thealmikey?source=rss-283d4a1eeb7e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:41:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thealmikey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Domain Expansion]]></title>
            <link>https://medium.com/@thealmikey/domain-expansion-3e68ffd4b1f2?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e68ffd4b1f2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[dataannotations]]></category>
            <category><![CDATA[jujutsu-kaisen]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 18:48:33 GMT</pubDate>
            <atom:updated>2026-09-04T19:04:09.403Z</atom:updated>
            <content:encoded><![CDATA[<p>Expanding What A Programmer Can Become</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E9kmfe0GXTvqiyyyS2MYgw.png" /></figure><p>I’m a big fan of Gojo, so this is probably an inevitable reference. 😄</p><p>For anyone unfamiliar with Jujutsu Kaisen, Domain Expansion is basically a character creating their own space where their abilities become overwhelmingly effective. The good guys have it. The bad guys have it too. Everyone gets a domain.</p><p><a href="https://www.youtube.com/watch?v=nmvkhLz8t7I">https://www.youtube.com/watch?v=nmvkhLz8t7I</a></p><p>Lately, I’ve been thinking about it as a metaphor for the modern software engineer.</p><p>Our default environment is shifting.</p><p>For a long time, we built our domains around programming languages, frameworks, databases, Git, Linux, cloud and CI/CD. We trained like samurai. Git became our nunchucks, Bash and CI/CD became something closer to taichi. There was something almost cinematic about becoming fluent with these tools.</p><p>Now the movie feels different.</p><p>The LLM sometimes feels less like a samurai weapon and more like a gun. A little more Rambo. Code flying everywhere, agents running around, quips from the model, and sometimes a storyline that’s hard to follow. 😂</p><p>But underneath all the noise, something interesting is happening.</p><p>I’ve been doing some data annotation work, and sometimes it genuinely feels like we’re helping fine-tune the thing that is changing our own profession.</p><p>At the same time, I’ve been diving much deeper into ML and LLMs. Hugging Face, Kaggle, Roboflow, Labelbox and a whole vocabulary that wasn’t really on my map a few years ago.</p><p>Real-world job scarcity has also forced an interesting shift. Software developers are increasingly becoming spec creators, problem framers and people who write prose that machines turn into software.</p><p>The programmer isn’t just temporarily writing a prompt. They’re trying to embody an LLM.</p><p>To think in terms of context, ambiguity, constraints, intent, evaluation and failure modes.</p><p>I recently read an article from the creator of a 1993 game describing how he used AI to recreate and port it.</p><p>Beautiful code written when I was literally a baby.</p><p>And then there was another layer to it: I was using AI to understand the article itself. Assembly, memory layouts, collision logic, old hardware and decades-old engineering decisions were being translated into concepts I could actually follow.</p><p>AI wasn’t just helping recreate the software.</p><p>It was helping me access knowledge that would otherwise have been outside my domain.</p><p>That feels like the real Domain Expansion.</p><p>Not abandoning what we learned, but finding new fields to feed from.</p><p>It reminds me of when I refused ear training while learning guitar because software could tell me if I was in tune. I thought the tool made the old discipline unnecessary.</p><p>Maybe the lesson isn’t to reject the tools.</p><p>It’s to learn enough that the tools become an extension of your ability rather than a replacement for understanding.</p><p>The domain is expanding.</p><p>And perhaps instead of Malevolent Shrine, bad guy’s domain expansion, we can get a Magnificent Shine. 😄</p><p>The frontier isn’t just replacing the programmer.</p><p>It’s expanding what a programmer can become.</p><p><strong>EDIT</strong></p><p><strong>Got a software project you’re working on, feel free to reach out.<br>I am a Fullstack Dev with years of experience and I have worked with AI/ML/LLMs and love tackling challening problems.</strong></p><p><a href="https://www.upwork.com/freelancers/michaelgikaru">https://www.upwork.com/freelancers/michaelgikaru</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e68ffd4b1f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[cosmic raft for the bruised ego]]></title>
            <link>https://medium.com/@thealmikey/cosmic-raft-for-the-bruised-ego-f87bf72f6b70?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f87bf72f6b70</guid>
            <category><![CDATA[metaphysical-poetry]]></category>
            <category><![CDATA[kenya]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tailwind-css]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 15:14:56 GMT</pubDate>
            <atom:updated>2026-01-11T15:16:40.597Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="man at sea on a raft, their clothes are ragged, holding picture of family, guitar on raft, sea monster shadow vaguely visible from a distance" src="https://cdn-images-1.medium.com/max/1024/1*t2Qz87sNLcp4ztOuAz0YCA.png" /></figure><p>She left.<br> Not dramatically. Not with a slammed door.<br> Just efficiently.<br> Like refactoring a life that no longer compiled.</p><p>The kid went with her.<br> I tell myself that’s temporary.<br> I tell myself a lot of things.</p><p>They laid me off last month.<br> The email was polite.<br> The AI is quite nice, actually.<br> Writes cleaner code.<br> Never drinks.<br> Never asks why we’re doing any of this.</p><p>My friend became a chef.<br> Did you know that?<br> He touches food all day.<br> Burns himself. Cuts himself.<br> People thank him to his face.</p><p>I build systems no one sees<br> and get thanked by dashboards.</p><p>Sometimes I envy him so much it feels physical,<br> pressure behind the eyes.<br> He smells like smoke and garlic.<br> I smell like old coffee and stale ambition.</p><p>Maybe we should have been sailors.<br> Honestly.<br> Deal with the old gods and the sea directly.<br> Let them break things honestly.</p><p>The sea doesn’t pretend.</p><p>The motivational speaker yells,<br> “We are purpose animals.<br> Storm animals.<br> Give us smooth water and we go insane.”</p><p>The inherited thirst answers back.<br> Old tankloads of wanting to be worshipped, respected.<br> Filtered through our fathers.<br> Renamed law.<br> Renamed progress.<br> Renamed dopamine.</p><p>So we thanked the gods for the seas where we could drink our fill.</p><p>The digital sea rose.<br> The physical one didn’t.<br> Lightning cracked,<br> and in the water a mechanical Cthulhu circled,<br> built in our labs,<br> watching us paddle our rafts<br> while we tossed our sacrifices overboard.</p><p>Then I remember her laugh.<br> My daughter’s laugh.<br> My lighthouse.<br> The way it pulled me back into my body,<br> like a checksum that still passed.</p><p>The mind is a strange thing.<br> We cling to memory loops.<br> We anesthetize ourselves with old joy.</p><p>I remember taking her to Sea World.<br> Then I remember I’m at sea,<br> and I’m sad again.<br> Hallucinating new pains.<br> Reading articles about AI futures.<br> Each one telling us to sit quietly<br> and wait for the second coming.<br> It’s almost religious.</p><p>All I can do is go feral.<br> Like an animal.</p><p>It’s fun when you visit the zoo.<br> It’s not fun when the zoo comes to you.<br> It’s not fun when you’re inside it,<br> waiting to be fed.</p><p>Maybe there’s medicine encoded in my DNA.<br> I’m done with updates and upgrades.<br> Maybe the answer is older.<br> Something primal.</p><p>Give me hands that remember climbing trees.<br> Feet that trust unstable ground.<br> A nervous system that knows<br> when to roar<br> because it’s hungry.</p><p>We’re still made in His image,<br> in love<br> and when angry!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f87bf72f6b70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Experimenting with Mill Build Tool: 1]]></title>
            <link>https://medium.com/@thealmikey/experimenting-with-mill-build-tool-1-127ea74c62ab?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/127ea74c62ab</guid>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[build-tool]]></category>
            <category><![CDATA[scala]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[maven]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Sun, 19 Oct 2025 14:49:28 GMT</pubDate>
            <atom:updated>2025-10-19T19:11:06.563Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing Mill out with Scala:</h3><p>Mill is a modern build tool for the JVM ecosystem with first-class support for Scala.</p><p>Mill uses plain Scala, unlike other build tools that rely on custom DSLs with hidden internals and unclear plugin mechanisms. Mill is designed to be fully extensible, without forcing you to reverse engineer plugins or parse configuration files whose rules/syntax are hard to follow.</p><p>This means if you hit a wall with a third-party plugin that may be outdated or poorly documented, with Mill you can just step inside the accessible API for the builds and tweak where needed(normal Scala programming with functions/loops/classes).</p><p>We will walk through creating a simple Scala 3 project using Mill.</p><p>Mill is under active development, and its feature set continues to grow rapidly. It is an excellent time to begin exploring it.</p><h3>Step 1: Create and Open an Empty Project Directory</h3><pre>mkdir learn1<br>cd learn1</pre><figure><img alt="Empty directory “learn1”" src="https://cdn-images-1.medium.com/max/1024/1*nZ2k_4uZ4upmJghAgwYj1Q.png" /></figure><p>Open this directory using IntelliJ IDEA. Ensure you have the Scala plugin installed. If not, IntelliJ will prompt you to install it when the project is detected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*QnA2ibvQYQ5GthMbZg3aMw.png" /></figure><h3>Step 2: Download and Enable Mill</h3><p>Mill does not require global installation. You can download it directly into your project folder.</p><pre>curl -L https://repo1.maven.org/maven2/com/lihaoyi/mill-dist/1.0.6/mill-dist-1.0.6-mill.sh -o mill<br>chmod +x mill<br>./mill version</pre><p>This initializes Mill and prepares the environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*lpvHSpnYkHQc9chKuiwJTg.png" /></figure><h3>Step 3: Explore Built-in Templates</h3><p>Mill provides a set of sample projects to help you learn through working examples.</p><pre>./mill init</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_pWNRyJNp7S2JCerW8Qlg.png" /></figure><p>You will see templates for Scala, Java, Kotlin, Python, and JavaScript project types. These examples can be used to quickly bootstrap a new project.</p><p>Example command to initialize a basic Scala project(you can try it later with a template you like). Lets go to Step 4 for now:</p><pre>./mill init scalalib/basic/1-simple</pre><h3>Step 4: Create the Build Definition</h3><p>Create a file named build.mill in the root of your project:</p><pre>package build<br>import mill.*, scalalib.*<br><br>object greet extends ScalaModule {<br>  def scalaVersion = &quot;3.7.1&quot;<br>  def mvnDeps = Seq(<br>    mvn&quot;com.lihaoyi::fansi:0.5.1&quot;,<br>    mvn&quot;com.lihaoyi::mainargs:0.7.6&quot;<br>  )<br><br>object test extends ScalaTests {<br>    def mvnDeps = Seq(mvn&quot;com.lihaoyi::utest:0.8.9&quot;)<br>    def testFramework = &quot;utest.runner.Framework&quot;<br>  }<br>}</pre><p>This build file defines a Scala module named greet with dependencies for command-line argument parsing and adding color to text in the terminal.</p><h3>Step 5: Write the Application Code</h3><p>Create the following file:</p><p>greet/src/Hello.scala</p><pre>package greet<br>import fansi._<br>import mainargs._<br><br>object Hello:<br>  @main<br>  def run(name: String = &quot;World&quot;): Unit =<br>    val msg = Str(&quot;Hello, &quot;) ++ Color.Green(name) ++ Str(&quot;! Welcome to Mill + Scala 3&quot;)<br>    println(msg)<br>  def main(args: Array[String]): Unit = ParserForMethods(this).runOrExit(args)</pre><p>Explanation:</p><ul><li>@main marks the entry point for Mill to run the program directly.</li><li>The name parameter has a default value.</li><li>The fansi library is used to add color to the output.</li><li>The mainargs library automatically handles command-line argument parsing.</li></ul><h3>Step 6: Run the Application</h3><p>To run the program without any arguments:</p><p>./mill greet.run</p><p>Output:</p><p>Hello, World! Welcome to Mill + Scala 3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*U8jsXPxHAaVRFjxlEwjUcg.png" /></figure><p>To pass a name argument:</p><p>./mill greet.run --name Mike</p><p>Output:</p><p>Hello, Mike! Welcome to Mill + Scala 3</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=127ea74c62ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Call Me By Your Name — Interesting Labels and Names in Software ]]></title>
            <link>https://medium.com/@thealmikey/call-me-by-your-name-interesting-labels-and-names-in-software-603196554adb?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/603196554adb</guid>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[anthropology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Fri, 04 Jul 2025 11:54:38 GMT</pubDate>
            <atom:updated>2025-07-04T11:54:38.710Z</atom:updated>
            <content:encoded><![CDATA[<h3>Call Me By Your Name — Interesting Labels and Names in Software 🎵</h3><p><em>A witty tour of the old ideas still haunting modern codebases.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*D1taz7Adaqn4quR0" /></figure><p>We’ll explore quirks, metaphors, and historic choices that once made perfect sense — but now mostly confuse developers trying to learn modern concepts. Each section will be its own short, sweet, and clever read. Here’s the first set of these tech relics, formatted as a snappy, readable mini-book for devs.</p><h3>🧠 Chapter 1: Why “Daemon”? Is My Code Possessed?</h3><p>The first time a junior dev sees the word <em>daemon</em>, they might imagine their background process is about to summon Beelzebub.</p><p>But no — this isn’t demonic possession. It’s MIT nerd humor from the 1960s. Daemons (yes, the spelling matters) were long-running helper processes that quietly did background tasks, like printing files or watching system time. The name came from <em>Maxwell’s Demon</em>, a thought experiment in physics — not religion.</p><p>But tell that to the poor beginner staring at a systemd crash report thinking they&#39;ve summoned a digital ghost.</p><p><strong>Modern Takeaway</strong>: Background workers, services, agents — any of those would be clearer in 2025. But <em>daemon</em> lingers, cloaked in lore.</p><h3>💾 Chapter 2: Why Is It Called a “Mount”?</h3><p>You’re learning filesystems, and suddenly your operating system wants you to <em>mount</em> something. What is this, medieval horseback combat?</p><p>Turns out, back in UNIX’s glory days, “mounting” referred to attaching a new filesystem (like a disk) into the master tree. It was a metaphor drawn from <em>mounting magnetic tape reels</em> onto drives — because yes, we once stored data on what looked like film canisters from a 70s sci-fi movie.</p><p>The concept stuck around. Now we’re mounting USB drives, network shares, and cloud buckets — even though nothing physical is involved.</p><p><strong>Modern Takeaway</strong>: Think of it like plugging a Lego piece into the global file tree. But maybe don’t imagine yourself on a horse.</p><h3>📞 Chapter 3: Why “Hang Up” a Network Socket?</h3><p>In networking, a connection can be “hung up” like a phone call. Makes sense… if you’ve ever <em>used a landline</em>.</p><p>Early computing used phone networks — literally. Dial-up modems screeched their way online through actual telephone lines. When the call ended, the modem would “hang up”. UNIX networking adopted the same metaphor when dealing with socket connections.</p><p>Even SIGHUP, the signal in Unix to indicate a hang-up, lives on—ironically now repurposed to tell daemons to reload their configs.</p><p><strong>Modern Takeaway</strong>: In code, hanging up is digital. But the lingo? Pure rotary phone nostalgia.</p><h3>📦 Chapter 4: Why Is a JavaScript Package Called a “Module”?</h3><p>JavaScript modules today are neat ES6 imports. But they didn’t start there.</p><p>The term <em>module</em> predates JavaScript by decades. It comes from 1960s-era modular programming ideas, where code was broken into independent “modules” for reuse and maintainability — think Lego blocks again, but with Fortran.</p><p>JavaScript <em>tried</em> to be modular, but early on it just wasn’t. We had to fake it with IIFEs, require(), and later Webpack hacks. When modules <em>finally</em> got native support, we still used the old term.</p><p><strong>Modern Takeaway</strong>: “Module” in JavaScript is both accurate <em>and</em> misleading, depending on what decade you’re referencing.</p><h3>🖥 Chapter 5: Why Is the “Terminal” Not a Terminal?</h3><p>You’re typing into a “terminal”, but you’re on a MacBook in 2025. What exactly is this thing?</p><p>Originally, a terminal was a <em>physical device</em> — a monitor and keyboard wired to a mainframe. Like a glorified keyboarded TV. It “terminated” at the end of the wire, hence the name.</p><p>Today’s terminal emulator is a program pretending to be that same device. Which is why it still acts like a green-screened antique when you mistype a command.</p><p><strong>Modern Takeaway</strong>: You’re not using a terminal. You’re pretending to pretend you’re using a terminal. Meta enough?</p><h3>🔁 Chapter 6: Why “TTY”? Is This Code Morse?</h3><p>Ever run into /dev/tty and wonder: why am I talking to an acronym?</p><p><strong>TTY</strong> stands for <strong>Teletypewriter</strong>, a mechanical beast used to send typed messages over telegraph lines. UNIX borrowed this term because its early user input/output came from actual teletype devices.</p><p>By the time we got virtual terminals, we’d already named them after the real thing. Now /dev/tty is just a digital ghost of that device, long dead but still respected like some ancient UNIX ancestor.</p><p><strong>Modern Takeaway</strong>: You’re not speaking to a teletype. But your system <em>thinks</em> you are, and that’s adorable.</p><h3>💣 Chapter 7: Why Does “Kill” Not Always Kill?</h3><p>You run kill, but your process is still alive. You think: <em>Should I try garlic next?</em></p><p>The kill command sends a <em>signal</em> to a process, asking it politely (or not) to shut down. But it’s only a request—unless you specify -9, the dreaded <em>SIGKILL</em>, which is more like &quot;kick down the door&quot;.</p><p>The name “kill” is a bit misleading — it doesn’t always kill. It nudges, pings, whispers… and sometimes, if ignored, it screams.</p><p><strong>Modern Takeaway</strong>: kill is really “send a message.” Just with an attitude.</p><h3>🧶 Chapter 8: Why Are Threads Called Threads?</h3><p>Multithreading isn’t about yarn. But the metaphor is ancient — spun from the days of early computing and even earlier mythology.</p><p>The <em>thread of execution</em> was described as a linear path through code, like a single string weaving its way through a program. Multiple threads = multiple strings in the loom, all woven together by the CPU scheduler.</p><p>It’s poetic. But when you’re debugging race conditions at 2am, it’s less tapestry, more tangled spaghetti.</p><p><strong>Modern Takeaway</strong>: Threads are paths, not fibers. Until they’re fibers. Then all bets are off.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=603196554adb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Coding with Digital Crack…Finding Nemo]]></title>
            <link>https://medium.com/@thealmikey/sh-coding-with-digital-crack-finding-nemo-466b9d4087b8?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/466b9d4087b8</guid>
            <category><![CDATA[llm-applications]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[funding]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[scala]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Sat, 28 Jun 2025 22:57:36 GMT</pubDate>
            <atom:updated>2025-06-28T23:04:48.558Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mad-Scientist Juniors, AI Hype, and Cult-Like Code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*N9blyEMEXczZvd8A" /></figure><p>Somewhere in your team, there’s a bright-eyed junior developer named Nemo. He wanted to help. He meant well. But now he’s 200 commits deep into building a domain-specific language for button clicks, consulting ChatGPT like it’s a divine oracle, and throwing around terms like “cofree comonads” to explain why your login page still isn’t deployed.</p><p>This all started so innocently. You said, “Let’s model the domain a bit more explicitly.” And maybe mentioned that side effects could be isolated. And that purity was cool. Now, Nemo is halfway to simulating a universe where every click event has moral weight</p><p>You begin to realize something: Rick and Morty, Doctor Who, and GitHub Copilot are shaping your team’s worldview more than any product roadmap ever has. And the worst part? You understand. It is tempting to chase elegance, simulate minds, or create a clean abstraction for everything. Who wouldn’t want to write code that feels like a mathematical proof?</p><p>Meanwhile, your real user base just wants to submit a form.</p><p>Nemo’s latest task was to add a toggle to the dashboard. He delivered an abstracted, modular event-handling engine with algebraic constraints and a recursive effect system that reifies toggle intentions into a monadic signal flow. It doesn’t work. But it is… impressive. And deeply unreadable.</p><p>This is what happens when LLMs whisper sweet abstractions in the ears of idealistic juniors. When every autocomplete makes it look easy to write tools that write tools that write themselves. Nemo genuinely believes he’s 10 PRs away from building Jarvis. Maybe he is. But right now, the staging environment is down, and marketing needs the banner changed by Thursday.</p><p>We keep forgetting that not all fish need organs. Not all simulations need to be real. Most of what we build doesn’t need internal logic that survives scrutiny by a cosmic auditor. The fish just needs to wobble. The app needs to work. The button needs to click. And sometimes, the fastest way there is a janky WordPress plugin that crashes every other weekend but raised a million dollars last week.</p><p>Functional programming has its place. So does AI. So does wild curiosity. But time is real. Deadlines are not theoretical constructs. They don’t yield to elegance. They pass.</p><p>If you want to save Nemo — and yourself — you don’t ban his idealism. You just anchor it. Guide it. Point out that sometimes a simple function is more powerful than a philosophical rabbit hole. That a useful illusion can matter more than internal truth. That great software feels alive not because it simulates everything, but because it simulates just enough, just right.</p><p>Let the fish wobble. Let the code run. Let Nemo ship. And when the app is live, and the dashboard loads, and the button toggles, then, sure — you can revisit the free monads.</p><p>But maybe, just maybe, you’ll realize you don’t miss them all that much.</p><p><strong>Practical Wisdom those who still have hope.</strong></p><p><strong>1.</strong> <strong>Your juniors don’t need to build Jarvis.</strong><br>They need to build something someone will use.</p><p><strong>2</strong>. <strong>Treat LLMs like glorified interns.</strong><br>Helpful. Confident. Occasionally delusional.</p><p><strong>3. Encourage curiosity. Guard against cults.</strong><br>Functional programming is a discipline, not a doctrine.</p><p><strong>4. Simulations should be fun, not faithful.</strong><br>Reality is a reference, not a requirement.</p><p><strong>5. Your job is to grow developers who know when to stop.</strong><br>Not just how to go deeper.</p><h3><strong>EPILOGUE</strong></h3><p><em>At www.Pinch-My.ai, we’re bravely exploring the intersection of human frustration and machine discomfort. Our flagship innovation? A neural network that recoils — just a little — when it senses your two fingers closing in. It doesn’t do anything useful. But it feels something. Kind of. For some reason it’s working, investors keep throwing money at us not to finish it. Maybe they’re afraid we’ll actually launch it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=466b9d4087b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manual for the Hopeful African Coder❤]]></title>
            <link>https://medium.com/@thealmikey/manual-for-the-hopeful-african-coder-0770d028bdb9?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/0770d028bdb9</guid>
            <category><![CDATA[depression]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[poverty-alleviation]]></category>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[psychology]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 18:26:25 GMT</pubDate>
            <atom:updated>2025-06-25T18:26:25.190Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pOnQ9SjZ0jlhvKoq" /></figure><p>I won’t lie to you.</p><p>Some mornings I stare at the terminal like it’s mocking me. Like it knows I spent the last hour patching together stack traces with no clue if the root problem is my code or just that my hotspot ran out again. My dev environment boots up slower than a 90s Nokia. And yet — here I am. Still typing.</p><p>If you’re reading this, you’ve probably already debugged code on a bench outside a cybercafé. You’ve probably stared into the open grave of another broken SDK while the sun sets behind corrugated rooftops. You know what it means to learn under weight. To balance dreams on top of bundles.</p><p>They told us the internet would equalize things.</p><p>They didn’t say it would come with latency, power cuts, and the haunting quiet of feeling invisible in a global room buzzing with accelerators, meetups, and men who already sold their third startup by the time they hit 26.</p><p>And yet — here <strong>you</strong> are. Still building. Still googling cryptic errors. Still bootstrapping your mind into something sharper than anyone expects.</p><h3>🧠 The Burden of Knowing Everything</h3><p>You don’t just want to code. You want to be good. Better. Maybe great. And the internet is cruel about greatness — it presents it like a buffet. Pick your poison: React, GraphQL, Docker, gRPC, WebAssembly, AI agents, all the new toys from men in black hoodies and white papers.</p><p>But here’s the lie: <strong>you don’t need to eat the whole buffet to feel full</strong>.</p><p>You don’t need to learn everything. You need to learn what <em>moves you</em>. What <em>roots you</em>. What makes you forget time when you’re debugging, designing, rebuilding. Find one hard corner of this vast machine — own it. Let it bleed into you like spice in hot oil. The rest will come, but the depth? The depth will make you dangerous.</p><h3>🌍 The Silence of No Scene</h3><p>I used to feel jealous of people who could “just go to a meetup” and stumble into a $150k job by chatting about their side project over coffee. I romanticized Palo Alto like a mirage. But here’s the thing no one tells you:</p><p><strong>Silicon Valley isn’t a place. It’s a mindset. A cadence. A feedback loop.</strong></p><p>And we can build that here. In Whatsapp groups, in dusty co-working spots, in Telegram channels where four devs pass around broken links to open-source gems. Our own rhythm.</p><p>Start by showing up online. Write threads that document your journey. Translate hard docs into stories your 18-year-old cousin in Kisumu can understand. Contribute a small patch to a repo no one maintains anymore — do it anyway.</p><p>You are not “behind.” You are <strong>forging culture in a place where none existed before.</strong></p><h3>💸 The Currency of Constraint</h3><p>I won’t glamorize poverty. There’s nothing sexy about skipping meals because your freelance gig ghosted you again. But constraint? <strong>Constraint is honest.</strong> It makes you resourceful. It makes you respect the machine.</p><p>We code like we cook — with leftovers, with hacks, with flavor.<br> We don’t spin up five cloud VMs for a microservice. We <strong>simulate it in our heads</strong>, jotting sequence diagrams on the backs of receipts.</p><p>While others brute-force their way through architecture, we meditate.</p><p>That’s not weakness. That’s <strong>craft</strong>.</p><h3>🧭 Mentorship in the Desert</h3><p>No senior dev. No lead to pair with. No one telling you if this pattern is smart or just spaghetti with a for-loop.</p><p>I know that silence. The haunting fear that you’re doing it all wrong. But I learned something over time: <strong>code reviews aren’t the only form of feedback</strong>. Feedback is everywhere if you know how to listen.</p><p>Your test suite tells you when you’re sloppy. Your logs whisper when you misunderstand a flow. Your future self, reading last month’s code, becomes the stern mentor you never had.</p><p>Build your own mirror.</p><h3>🛠️ Building with Soul, Not Stack</h3><p>Tech Twitter will make you think you’re irrelevant if you’re not shipping React/Next.js apps on edge functions. That your worth is your stack.</p><p>But here? Here in the villages where people still share devices, where feature phones are king, where offline-first isn’t a trend but a <strong>requirement</strong> — you realize something:</p><p><strong>The tech that matters is the tech that lands.</strong></p><p>That landing page doesn’t have to be pretty — it has to be useful. That app doesn’t need 60FPS transitions — it needs to work on Android 6 with no updates. That script that syncs stock between your auntie’s two shops? That’s infrastructure.</p><p><strong>Solve local problems with global skill.</strong> That’s power.</p><h3>🔥 Invisible but Loading</h3><p>There will be months where it feels like nothing’s happening. No one’s clapping. No stars. No replies. No job offers.</p><p>But that doesn’t mean you’re idle. You’re compiling. Quietly.</p><p>Every hard bug is a rep. Every failed deploy is a scar. Every skipped party because you were too deep in the debugger is a chapter.</p><p>You’re not lost. You’re <strong>loading the kind of dev no one sees coming</strong>.</p><h3>✊🏾 A New Kind of Hacker</h3><p>You’re not the hoodie-wearing cliché.</p><p>You’re the barefoot problem solver who understands how people work.<br> You’re the kid who learned logic from fixing your dad’s radio.<br> You’re the builder who sees a broken education system, and thinks, “maybe I could automate just one piece of it.”</p><p>Your compilers are slow. Your internet is worse. But your <strong>instinct is elite</strong>.</p><p>Because when the world told you, “this isn’t built for you,”<br> you opened the hood anyway.</p><h3>🎤 Final Words From the Trenches</h3><p>I’m not writing this from a yacht. I’m writing this between Git pulls and anxious thoughts.<br> I’m still figuring it out too. But I know this:</p><p>Africa doesn’t need more hype. It needs more builders. More storytellers. More source code. More bad prototypes that become good ones. More soldiers like you.</p><p>So write the code. Write the blog. Open the PR.</p><p>Let the world hear <strong>the hum of the continent compiling.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0770d028bdb9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: A Taste of Grace — How We Got Here, and Why We Shouldn’t Look Away]]></title>
            <link>https://medium.com/@thealmikey/part-1-a-taste-of-grace-how-we-got-here-and-why-we-shouldnt-look-away-6c4cd5475ed0?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c4cd5475ed0</guid>
            <category><![CDATA[students]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[science-education]]></category>
            <category><![CDATA[kenya]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Sat, 21 Jun 2025 18:36:38 GMT</pubDate>
            <atom:updated>2025-06-21T18:36:38.891Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1: A Taste of Grace — How We Got Here, and Why We Shouldn’t Look Away</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xuyE3mLOcMnNnArK" /><figcaption>Artificial Intelligence Future</figcaption></figure><p><strong>There is a whisper in the bloodstream of humanity — and it sounds like this: <em>We made it.</em></strong></p><p>Not because we conquered everything. Not because we’re at the top. But because we’ve survived long enough to pass the baton. A few thousand years ago, we stared at the stars and made stories. A few hundred years ago, we found microbes, and then fire in wires, and later, a vaccine that paused a plague.</p><p>Today, that baton is AI.</p><p>But before we touch this next torch — let’s take a moment to recognize what we’re holding.</p><h3>The Ordinary Miracles That Got Us Here</h3><p>Take <strong>soap</strong>, for instance. The humble bar. In its own quiet way, it halved infant mortality and doubled lifespans. Before soap, we buried children like seasons. Afterwards, we had enough generations survive to start <em>remembering</em> what life was for.</p><p>Or <strong>antibiotics</strong> — a tiny mold that told death: “Not yet.” Penicillin did more for human productivity than all the kings and empires of Europe combined. It let us fix teeth, perform surgeries, survive wars, and raise families without funerals before first birthdays.</p><p>Or <strong>electricity</strong>. A Promethean flame we called “current.” We poured it into wires, walls, cities — then screens. And in those screens came <strong>music</strong>. Not just Mozart or Bob Marley — but <em>you</em>, in your room, discovering who you are through vibrations no one else hears the same way.</p><p>These are irreversible gifts. No one who has seen the light bulb asks to return to candles. No one who’s heard “Redemption Song” on a quiet night thinks silence is the superior technology.</p><p>So why do we hesitate with AI?</p><p>Why is this next fire, this next enzyme, treated with more dread than delight?</p><h3>The Fear Beneath the Algorithm</h3><p>Because this time, the change is <em>within</em> us.</p><p>Soap didn’t threaten our identity. Antibiotics didn’t automate our imagination. Electricity didn’t compete to be funnier than your favorite uncle.</p><p>AI? It finishes your sentences.</p><p>It guesses your next idea.</p><p>It offers you a draft of your thoughts — before you’ve even fully had them.</p><p>And it’s tempting to recoil. To cry “cheating!” or “blasphemy!” or “soulless mimicry!” But let’s be honest. What is more human than inventing something that <em>remembers</em> better than us? Something that <em>heals</em> faster, <em>responds</em> kinder, or <em>learns</em> without sleep?</p><p>If this is cheating, it’s the kind life itself has been doing for eons: evolving new organs for new challenges.</p><p>We’re just building them outside the body now.</p><h3>To the Young Minds of Africa: You Are Not Late</h3><p>If you’re a young Kenyan dev, doctor, engineer, or dreamer — you may feel like you’re arriving at the end of the party. AI models are already writing code. Diagnosing skin diseases. Composing symphonies. Even helping prosecute war crimes.</p><p>And here you are — scrolling, uncertain, maybe behind on some new library or too busy paying rent to go full polymath.</p><p>Let me offer you a different story:</p><p><strong>You’re right on time.</strong></p><p>Why? Because the most important skill right now isn’t mastery — it’s <em>symbiosis</em>.</p><p>You don’t need to memorize all of medicine. You need to ask better questions, and train an assistant to help you answer them in minutes instead of years.</p><p>You don’t need to out-code a machine. You need to know what to build, <em>for whom</em>, and <em>why it matters</em>. The syntax is easy. The insight? That’s where you live.</p><p>And you don’t need to fear AI’s power. You need to <em>wield</em> it — with humility, creativity, and the inherited fire of ancestors who survived drought, colonialism, collapse, and came out the other side with laughter still on their lips.</p><h3>The Greatest Form of Gratitude is Continuation</h3><p>To embrace AI isn’t betrayal.</p><p>It’s <em>thanksgiving</em>.</p><p>A thank-you to every farmer who planted without certainty. To every healer who treated wounds without anesthesia. To every teacher who taught before Google. To every rebel who dared to say “we deserve better.”</p><p>We’re their echo. Their recursive function.</p><p>And now, we get a glimpse into something they could only call <em>magic</em>.</p><p>An agent that helps you reason. A code interpreter that solves your bug. A writing partner that sounds like your better self. A diagnostic tool that helps stop a disease <em>before</em> it costs a life.</p><p>Is that not a small taste of grace?</p><p>Is that not a <em>drop from the fountain of heaven</em>, disguised as API calls and transformer models?</p><p>Let’s not waste it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c4cd5475ed0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Neat Drink in a Dirty World]]></title>
            <link>https://medium.com/@thealmikey/naa-neat-drink-in-a-dirty-world-1b5e7a987ac3?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5e7a987ac3</guid>
            <category><![CDATA[addiction]]></category>
            <category><![CDATA[kenya]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[government-and-politics]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Wed, 11 Jun 2025 23:22:24 GMT</pubDate>
            <atom:updated>2025-06-11T23:22:47.755Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RbMGk9RAoQLrOROy" /></figure><p>There are nights I enter rooms angry and forget why.</p><p>It’s not denial — I’ve outgrown the luxury of pretending. It’s logistics. The brain learns to budget. Mine files rage in the deep archive, buries it under invoices, email threads, headlines, a half-written book about system collapse and stoic control.<br> So I show up to Sanctuary again. Not for answers. Not for company. Certainly not for resolution. Just… for noise sharp enough to press against the static in my head.</p><h3>This Place Again</h3><p>Sanctuary is one of those bars that wants to be misunderstood. The lighting is soft in that “we gave up trying” kind of way. It smells like warm regret and a mop that needs early retirement. The regulars are repeat offenders — of opinion, of posture, of failed punchlines.</p><p>I go because the music isn’t too loud. Because the barstools are firm. Because my face is symmetrical enough to earn space but not attention.</p><p>I sit.</p><h3>Enter Hank</h3><p>Hank talks like he’s trying to build a sentence that will finally collapse capitalism. He’s mid-monologue when I order. Something about finance being the spiritual disease of modern man.</p><blockquote><strong><em>Hank:</em></strong><em><br> “It’s the externalization of value, you see — commodification of dignity. You’re not </em>you<em> anymore. You’re a </em>net gain<em>.”</em></blockquote><p>I nod. Not agree — just acknowledge. Hank needs an audience, not a sparring partner.</p><blockquote><strong><em>Me:</em></strong><em><br> “Mm. I get dividends. I miss dignity.”</em></blockquote><p>He doesn’t laugh. He never does. He hears irony like it owes him money.</p><h3>Ivy Shows Up</h3><p>Ivy always shows up sideways. Like she’s entering a scene halfway through a better one. She orders something fiery and liquid courage-adjacent.</p><blockquote><strong><em>Ivy:</em></strong><em><br> “Y’all still debating the death of the soul or whatever?”<br> </em><strong><em>Hank:</em></strong><em><br> “We’re tracing decline. Which you’re proof of.”<br> </em><strong><em>Ivy:</em></strong><em><br> “Touché. You want a real crisis, try affording brake pads.”</em></blockquote><p>Her words hit like sparring gloves. My kind of language: sharp, rhythmic, unsentimental. I like her cadence, not her conclusions.</p><p>I look down at my drink. Neat. Always neat. Chaos should be sipped, not spilled.</p><h3>Static Between Us</h3><p>They talk. I listen in parentheses.</p><blockquote><strong><em>Hank:</em></strong><em> full of clauses, triple-scoop sentences, Marxism dressed in trench coat drama.<br> </em><strong><em>Ivy:</em></strong><em> one-liners and lived-in pain, practical like duct tape over a bullet wound.</em></blockquote><blockquote><strong><em>Me:</em></strong><em> I speak only when the silence threatens to suffocate itself. And even then, I edit aloud.</em></blockquote><h3>Silas, The Gravity</h3><p>Silas owns the place. He rarely speaks, but when he does, it’s to shift the conversation just enough to remind us who pays the light bill. His presence is posture alone — a man who’s found dignity not in ideas, but in managing their aftermath.</p><p>He pours a glass in front of me without asking. Knows my rhythm. One every forty minutes. Like a metronome resisting entropy.</p><blockquote><strong><em>Silas:</em></strong><em><br> “You’re quieter tonight.”<br> </em><strong><em>Me:</em></strong><em><br> “I’m not quieter. Just less convinced I need to be heard.”</em></blockquote><p>That gets a look from Ivy. A flicker of something between interest and self-defense.</p><h3>The Boil</h3><p>Tensions build like soup left too long — thickening, darkening, threatening to burn. Hank’s on his third drink and speaking in paragraphs again.</p><blockquote><strong><em>Hank:</em></strong><em><br> “This generation — no reverence. No memory. They inherit, and think they invented.”</em></blockquote><blockquote><strong><em>Ivy:</em></strong><em><br> “You mean like you quoting books no one asked about?”</em></blockquote><blockquote><strong><em>Hank:</em></strong><em><br> “I’ve read things that could burn your name off the map.”</em></blockquote><blockquote><strong><em>Me:</em></strong><em><br> “You say that every week.”</em></blockquote><p>There’s a pause. That kind of pause. The kind that tastes like splinters.</p><h3>The Edges We Pretend Not to See</h3><p>There’s something cruel about being articulate when the world is burning. Like showing up to a funeral in Versace.<br> Hank hates that I sound composed. Ivy mistrusts that I don’t flinch when provoked.</p><p>They think I haven’t felt what they’ve felt. Maybe they’re right.<br> But that’s not the point. The point is I <em>didn’t stop</em> when I felt it.</p><h3>Closing Time</h3><p>The night folds back into its creases. Hank storms out before the check. Ivy lingers but doesn’t say goodbye. Silas wipes the bar and flips a chair.</p><blockquote><strong><em>Silas:</em></strong><em><br> “Same time next week?”<br> </em><strong><em>Me:</em></strong><em><br> “Unless I remember what I’m mad about.”</em></blockquote><p>I step out into the cold. My coat too thin. My thoughts too dressed up. The city hums its ongoing electricity. And in that hum, I almost hear it — whatever it was I came here forgetting.</p><h3>Footnote</h3><p>They say repression is the enemy of truth.<br> But I say repression is just the mind setting boundaries.</p><p>And if you listen closely enough — between the debates and diatribes, the sermons and snark — you’ll hear it too. That quiet little whisper:</p><blockquote>You survived another evening without becoming them.</blockquote><p>That’s enough, for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5e7a987ac3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you swallow a whole Elephant?Byte at a time]]></title>
            <link>https://medium.com/@thealmikey/how-do-you-swallow-a-whole-elephant-byte-at-a-time-43d4629b0883?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/43d4629b0883</guid>
            <category><![CDATA[nairobi]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[biotechnology]]></category>
            <category><![CDATA[kenya]]></category>
            <category><![CDATA[disability]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Sat, 07 Jun 2025 22:19:42 GMT</pubDate>
            <atom:updated>2025-06-07T22:19:42.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z7V6u64TzfNystQV" /></figure><p>It It starts with a walk.</p><p>Tom Mboya Street buzzes like a motherboard — wires, signals, traffic. I dodge a boda-boda, step over a puddle, and sip thick roadside chai, balancing hope and hustle. My phone, barely charged, pings with another AI blog post. Something about a startup using neural networks to detect eye disease. Another alert: someone just released an open-source tool that turns Kenyan Sign Language into text.</p><p>I pause.</p><p>This isn’t just hype anymore. This is real.</p><h3>Beneath the Noise, a Pattern</h3><p>From the printing press to the internet, each generation has had to climb their own mountain of confusion. Ours? It speaks in Python and thinks in vectors.</p><p>But if you zoom out far enough, you see the same old rhythm: Pain. Progress. Resistance. Discovery.</p><p>And now, here in Nairobi, at the edge of this AI wave, we get to choose — do we freeze, scroll endlessly, and feel left behind? Or do we build something that no one has dared dream of before?</p><h3>Why This Time is Different</h3><p>Gutenberg didn’t know about the smartphone.</p><p>Ada Lovelace didn’t expect deepfakes.</p><p>Alan Turing didn’t imagine transformers helping kids in Kibera learn algebra in Swahili.</p><p>But we? We live at the intersection. The timelines are collapsing. Research that used to take years now takes months. Sometimes days. Sometimes… minutes.</p><p>OpenCV, the humble computer vision library, can now help the visually impaired navigate matatu stages with image-to-speech feedback. The same tech can convert sign language into real-time voice — bridging decades of exclusion.</p><p>In pharmaceutical labs across the globe, AI models are discovering molecules faster than ever. Faster than humans. Faster than HIV. Faster than sickle cell.</p><p>Material science is getting a boost too. Labs are experimenting with AI-predicted compounds that break down plastic waste or speed up plant growth. Imagine that: AI models trained on chemistry datasets helping us <em>grow food</em> faster, cleaner, smarter.</p><p>Imagine a Kenya where hunger is optional. Where waste doesn’t pile. Where disability doesn’t mean exclusion.</p><p>Now stop imagining.</p><p>It’s already starting.</p><h3>The Unsung Infrastructure</h3><p>Of course, the miracles don’t come from nowhere.</p><p>They’re built on quiet things: open-source libraries, dusty terminals, 2am bug fixes by a dev in Nyeri. They’re held up by fiber cables under oceans and underpaid sysadmins keeping servers running in Johannesburg, Berlin, and Tokyo. The people behind the code, often unseen, sometimes unpaid, always essential.</p><p>When you fork a repo, contribute a fix, write a tutorial in Sheng, you’re part of that invisible scaffolding. When you teach your cousin Git, or help your friend debug a TensorFlow install, you’re greasing the wheels of progress.</p><p>Every keypress counts.</p><h3>What They Didn’t Predict</h3><p>You see, the old futurists had charts, predictions, models. They imagined a world of flying cars, robot butlers, and space colonies.</p><p>They didn’t see Nairobi coders fine-tuning Swahili LLMs.</p><p>They didn’t see youth training AI on indigenous crops or designing peer-to-peer apps to distribute food surplus across counties. They didn’t see African researchers using language models to parse years of health data and crack patterns even governments missed.</p><p>They didn’t see you.</p><p>But we do.</p><h3>From Nairobi, With Light</h3><p>This is not a call to worship AI.</p><p>It’s a call to <em>use it</em>.</p><p>Use it to heal. To clean. To translate. To simplify. To inspire. To teach. To amplify the dreams of kids in remote classrooms and the wisdom of farmers in arid lands.</p><p>Use it to turn research papers into Swahili radio scripts. Use it to map informal settlements. Use it to tell our stories louder, clearer, prouder.</p><p>Don’t let fear freeze you. Don’t let the hype distract you.</p><p>Let the tools become your brush. Let the process guide your hand.</p><h3>Trust the Process (Revisited)</h3><p>You’re not just “learning tech.” You’re walking a well-trodden, ancient road of stubborn hope.</p><p>From scribes to servers, from fire to fiber, from myths to models — we’ve always built tools to amplify what it means to be human.</p><p>This is no different. Except now, you hold the torch.</p><p>Let them call you a dreamer. Let them say it’s too late. Let them doubt. But keep going. You never know who you’ll inspire, who you’ll help, what door you’ll open.</p><p>Because one day, someone will ask what it felt like to be Kenyan during the AI dawn.</p><p>And I hope you’ll say:</p><blockquote><em>“We were broke. We were brilliant. We were builders. And we changed the world.”</em></blockquote><p><strong>Trust the process.</strong></p><p>The future is still wet cement. Bring your chisel.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43d4629b0883" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Joe Rogan vs Maasai Kenyan Techie]]></title>
            <link>https://medium.com/@thealmikey/joe-rogan-vs-maasai-kenyan-techie-40dc6749024e?source=rss-283d4a1eeb7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/40dc6749024e</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[biotechnology]]></category>
            <category><![CDATA[maasai]]></category>
            <category><![CDATA[china]]></category>
            <dc:creator><![CDATA[Michael Gikaru]]></dc:creator>
            <pubDate>Wed, 04 Jun 2025 00:20:02 GMT</pubDate>
            <atom:updated>2025-06-04T00:20:02.287Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>[Camera on. Studio lit. Elk jerky on table. Joe leans in like he’s about to ask if your entire continent has Wi-Fi. I lean back, fake-calm, wondering how I got here.]</blockquote><p><strong>Joe Rogan:</strong> So you’re from Africa, right?</p><p><strong>Me (smiling, tensing):</strong> I’m from Kenya, yeah. Born in Nairobi. Raised by mismatched USB cables and pirated software.</p><p><strong>Joe:</strong> That’s wild, man. You think AI could help… like, cure Ebola?</p><blockquote>He says this earnestly, like he’s asking about protein folding but also war crimes. I pause, consider how to respond without either confirming a stereotype or canceling myself.</blockquote><p><strong>Me:</strong> I mean… theoretically, sure.<br> Predictive diagnostics, genomic modeling, AI-designed antibodies… there’s a lot of promise.<br> But you know what we <em>really</em> need AI to do?</p><p><strong>Joe (leans forward, excited):</strong> What?</p><p><strong>Me:</strong> Keep politicians from stealing the hospital funds.<br> Honestly, that’d cure half our diseases.</p><p><strong>Joe:</strong> Damn. That’s deep.<br> You know, I read somewhere — Maasai warriors used to train by fighting lions.<br> You think I could take one in a cage match?</p><blockquote>I blink twice. Realize he’s not joking. Smile like a diplomat trapped at brunch.</blockquote><p><strong>Me:</strong> Well… the lion or the Maasai?</p><p><strong>Joe (laughing):</strong> Both!</p><p><strong>Me:</strong> Ah, yes. The <em>rare Joe Rogan double feature</em>.<br> Honestly, I think you’d get smoked by the <em>grandmother</em> of a retired Maasai warrior.<br> And she’d make you apologize while doing it.</p><blockquote>He laughs. I laugh. Everyone is being polite and mildly terrified.</blockquote><p><strong>Joe:</strong> So like — how’s tech over there? You guys building stuff?</p><p><strong>Me:</strong> Oh, totally.<br> There’s a guy in Uganda doing AI for crop prediction.<br> A woman in Nigeria built a speech-to-text app for Yoruba dialects.<br> I did standup at a tech meet-up in Nairobi once.<br> Had to follow a guy demoing his crypto wallet that works on a dumbphone.</p><p><strong>Joe:</strong> That’s insane.<br> You guys are doing comedy <em>and</em> AI?</p><p><strong>Me:</strong> We multitask.<br> Poverty builds character.<br> And punchlines.</p><p><strong>Joe:</strong> So what do you see AI doing for the future of Africa?</p><blockquote>Now he’s in Serious Mode. This is when you give the TEDx-worthy answer. But instead…</blockquote><p><strong>Me:</strong> Honestly?<br> Helping African aunties finally win arguments on WhatsApp.<br> That’s where the real impact is.<br> Imagine a GPT that can translate “just checking on you” into “why aren’t you married yet?”</p><p><strong>Joe:</strong> That’s incredible.<br> Could AI also stop tribal raiding and conflict?</p><p><strong>Me:</strong> (slowly)<br> In theory, yes.<br> In practice… depends if the AI is open-source or IMF-funded.</p><blockquote>We both stare into the existential void for a moment.</blockquote><p><strong>Joe (gently):</strong> You ever feel like you’re part of something big?</p><p><strong>Me:</strong> Every time I touch a framework built in California<br> and run it on a laptop bought in Dubai<br> to deploy a side project hosted in Germany<br> with a front-end designed by a Kenyan kid watching a React tutorial at 2am on mobile data — <br> yeah.<br> It’s big.<br> It’s broken.<br> It’s beautiful.</p><blockquote>Joe goes quiet. Sips his caveman mushroom tea. I sip my imposter syndrome. We vibe.</blockquote><p><strong>Joe (softly):</strong> You ever think the world’s gonna be okay?</p><p><strong>Me:</strong><br> No.<br> But I think <em>we</em> might be.<br> If we keep telling jokes.<br> And building things.<br> And not trying to MMA fight entire ethnic communities.</p><blockquote>We laugh. Freeze-frame. Cut to outro music. Sponsored by whatever LLM-based productivity app is trending on LinkedIn this week.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40dc6749024e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>