<?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 Caleb Wodi on Medium]]></title>
        <description><![CDATA[Stories by Caleb Wodi on Medium]]></description>
        <link>https://medium.com/@calchiwo?source=rss-e9c05a661b7f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*11ShJnVvENlYoPl5jA1R9w.jpeg</url>
            <title>Stories by Caleb Wodi on Medium</title>
            <link>https://medium.com/@calchiwo?source=rss-e9c05a661b7f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:50:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@calchiwo/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[I Removed An Entire Implementation Of My System To Fix An Architectural Duplication That Was…]]></title>
            <link>https://medium.com/@calchiwo/i-removed-an-entire-implementation-of-my-system-to-fix-an-architectural-duplication-that-was-020bff141577?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/020bff141577</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Thu, 30 Apr 2026 12:31:46 GMT</pubDate>
            <atom:updated>2026-04-30T12:31:46.913Z</atom:updated>
            <content:encoded><![CDATA[<h3>I Removed An Entire Implementation Of My System To Fix An Architectural Duplication That Was Painful To Maintain Alone (Deleted ~1300 lines)</h3><p><strong>The real problem with duplication</strong></p><p>Having two implementations of one system didn’t look like a problem to me at first, I built it once and it worked, then I re-implemented the same system again in another language, keeping feature parity and that also still worked.</p><p>I’m building ExplainThisRepo, a CLI tool for understanding unfamiliar codebases that shows you where to start, what matters and what to ignore using real signals; entrypoints, configs, dependencies, manifests, not blind AI guessing</p><p>Before now every time I ship a feature I’m not building it once, I’m actually building it twice, same with bugs, I’m not fixing them once, I’m fixing them twice</p><p>Initially it seemed manageable, but what I had actually created was two sources of truth.</p><p>And now I also have to make sure both implementations behave the same way in different languages: Python and TypeScript</p><p>They were not wrappers of each other, they were just two independent systems with the same features, behavior, outputs and edge cases, implemented differently in each language, and I had to keep aligning them and maintaining ecosystem feature parity.</p><p>That slowed everything down and was very painful to maintain alone</p><p>At some point, I stopped moving fast not because the system was complex, but because I was maintaining two of everything.</p><p>So I removed the duplicate TypeScript implementation, deleted ~1300 lines and made Python the only core implementation and source of truth, Node now only bundles into npm distribution and launches the Python binary, it no longer runs any logic, all the logic lives in Python.</p><p>All the CLI behavior, repo analysis, providers, output, everything, runs inside the prebuilt Python binary. It runs without requiring Python installed on the user’s machine. No duplication, one system</p><p>Link to PR: <a href="https://github.com/calchiwo/ExplainThisRepo/pull/208">https://github.com/calchiwo/ExplainThisRepo/pull/208</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3JftdtGgSksr2Ctr0H2u9Q.png" /></figure><p><strong>Why Python became the core implementation</strong></p><p>The decision was not about “which language is better”, it was:</p><p>Which implementation should remain as the single source of truth?</p><p>One system should have one source of truth, everything else is distribution.</p><p>I chose Python because it’s the correct long-term place for the system to live. It was already the implementation I was building on most actively, new features were landing there first and that’s where the system was already evolving.</p><p>In short Python was where the core logic was stable and iteration was fastest</p><p>Keeping TypeScript as the core would mean either shifting development entirely to it or continuing to duplicate work, both increase long-term cost.</p><p>So instead of moving the system, I kept it where it was already being developed, removed the TypeScript implementation, and made Python the only core implementation, Node now just acts as a launcher for the Python binary and distribution.</p><p><strong>Why maintaining both breaks down over time</strong></p><p>At that point, it was tempting to say:</p><p>“I’ll just keep both implementations and manage them”</p><p>and yeah that works early but it doesn’t scale.</p><p>Because the real cost isn’t just duplication, it’s coordination, you now have to keep both implementations aligned, every change now means doing the same work twice, making sure behavior matches, remembering what changed where, and that turns simple changes into tracking problems, so you hesitate to ship, small differences start creeping in, edge cases multiply and over time the system becomes harder to trust, harder to maintain and slower to evolve.</p><p>This gets worse when you’re maintaining it alone, there’s no distribution of effort, you’re the one building, reviewing and maintaining consistency, and at some point it slows everything down not because the system is complex, but because you’re maintaining two of everything.</p><p>The hidden trap is this: duplication creates the illusion that things are fine, but in reality it removes clarity, you no longer have one system (or single source of truth) you can reason about, you now have two systems that must stay consistent, and that is a fundamentally harder problem.</p><p><strong>What this actually is</strong></p><p>This isn’t just a refactor, it’s a correction, I moved from a multi-runtime tool to a single-engine product with a distribution wrapper, the mistake was letting the same system exist in multiple places, so I changed how it’s distributed, Node no longer re-implements anything, it just detects your OS, picks the right binary and executes it as a separate process.</p><p><strong>When to use this approach</strong></p><p>This pattern works when:</p><p>• you need to distribute across multiple ecosystems without rewriting the system</p><p>• the interface is clear and bounded (clear inputs, a defined process and predictable outputs)</p><p>• cross-runtime execution is acceptable</p><p>Common cases:</p><p>• CLI tools</p><p>• automation tools</p><p>• backend services with well-defined boundaries</p><p>• internal tools shared across environments</p><p><strong>When not to use it</strong></p><p>This pattern does not fit when:</p><p>• you’re building libraries that must run inside a specific runtime</p><p>• tight, in-process integration is required</p><p>• performance is sensitive to process startup or cross-runtime latency</p><p>• the system relies heavily on features tied to a specific runtime</p><p><strong>The test</strong></p><p>Before you build the same system twice, ask:</p><p>If I change this tomorrow, do I have to update it in more than one place?</p><p>If the answer is yes, you don’t have one system, you have duplication.</p><p>And if you keep going, you’re choosing coordination over progress.</p><p>You don’t fix duplication by maintaining it better, you fix it by removing the second place it exists</p><p><strong>Tradeoffs</strong></p><p>This change simplifies the system, but it isn’t free, bundling Python into the npm package increases the binary size so install size goes up compared to a pure Node tool, startup also has a cost because the Node launcher starts a separate Python process which adds extra startup time before execution, cross-platform support becomes more complex since you now need to build and maintain binaries for different operating systems and architectures, and debugging is less direct because issues can sit across the boundary between Node and Python, so you end up tracing problems across two environments.</p><p>These are real costs, but they are contained costs, not duplicated logic, and I chose to pay them because they scale better long-term than maintaining two implementations of the same system.</p><p><strong>The conclusion</strong></p><p>Maintaining both is not something you can sustain, the cost keeps increasing over time until it forces a decision, you either accept the growing cost or enforce a single source of truth, I chose the second.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=020bff141577" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Text Actually Works on the Web: Encoding, Decoding, and Why It Breaks]]></title>
            <link>https://medium.com/@calchiwo/how-text-actually-works-on-the-web-encoding-decoding-and-why-it-breaks-793d0c50c491?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/793d0c50c491</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 17:56:40 GMT</pubDate>
            <atom:updated>2026-03-31T17:56:40.694Z</atom:updated>
            <content:encoded><![CDATA[<p>How Text Actually Works on the Web: Encoding, Decoding, and Why It Breaks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/716/1*Z27kgstnCjAKpFA9h7ZIpw.jpeg" /></figure><p>Encoding is converting human-readable characters into bytes<br>Think: English → numbers</p><p>Whereas, Decoding is converting bytes back into characters<br>Think: numbers → English</p><p>When you write code:</p><p>You type:<br>Hello</p><p>Your editor encodes it into bytes and stores it on disk.</p><p>When the browser reads the file:</p><p>It reads bytes like:<br>72 101 108 108 111</p><p>Then decodes them back and shows:<br>Hello</p><p>What exactly is really UTF-8?</p><p>UTF-8 is a rule book that defines how characters (represented as Unicode numbers or code points) encode into bytes stored in the disk in the writing phase (by the editor) and how the bytes stored in the disk decode into characters in the reading phase (by the browser).</p><p>Simply put, UTF-8 is a rulebook that defines how Unicode code points are encoded into bytes and decoded back into characters.</p><p>It uses 8-bit units (bytes) and uses between 1 and 4 bytes per character.</p><p>Important idea</p><p>Computers store bytes. What we see as &quot;characters&quot; are just interpretations of those bytes the computer stores</p><p>How does the browser know how to decode?</p><p>That’s what this does:</p><p>&lt;meta charset=&quot;UTF-8&quot;&gt;</p><p>It tells the browser which encoding to use.</p><p>The same bytes decoded with a different encoding can produce completely different text</p><p>Bytes: 195 169</p><p>UTF-8 → é <br>Windows-1252 → Ã©</p><p>What if charset is removed?</p><p>The browser falls back to a decision chain:</p><p>1. HTTP headers<br>2. Byte Order Mark (BOM)<br>3. Guessing<br>4. Default encoding</p><p>This can lead to incorrect text rendering and inconsistent results across browsers and systems</p><p>Where ASCII, Unicode, and UTF-8 fit</p><p>ASCII said &quot;let us assign numbers to a small set of characters&quot;</p><p>Unicode came and said &quot;let us assign numbers to ALL characters globally&quot;</p><p>UTF-8 said &quot;let us define how those numbers (assigned to characters i.e. Unicode numbers) encode into one or more bytes (each byte is 8 bits)&quot;</p><p>Humans and engineers were the ones who assigned numbers to characters. And these assignments are called encoding standards:<br>Character encoding (Unicode) → assigns numbers<br>Encoding format (UTF-8) → turns numbers into bytes</p><p>Bits and Bytes</p><p>A bit is a 0 or 1</p><p>A byte is 8 bits</p><p>A byte can represent values from 0 to 255</p><p>Final idea</p><p>Files are stored as bytes.<br>Meaning comes from how those bytes are decoded.</p><p>These are my own way I use to understand charset, UTF-8, Unicode, ASCII, encoding, decoding, bytes, bits, standards</p><p>And if you found this breakdown helpful...<br> I’m documenting my understanding of how systems on the web actually work: https://github.com/calchiwo/WodiWeb</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=793d0c50c491" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Git Keeps Tracking Files You Told It to Ignore]]></title>
            <link>https://medium.com/@calchiwo/why-git-keeps-tracking-files-you-told-it-to-ignore-e7be4e2b89a8?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7be4e2b89a8</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 17:14:22 GMT</pubDate>
            <atom:updated>2026-03-25T17:27:40.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*kVWc3_7Ytd8fPfJ8jwTIxA.jpeg" /></figure><p>You add .<em>env </em>to <em>.gitignore</em></p><p>Run <em>git status</em></p><p>it still shows up</p><p>At this point it just looks like git is ignoring you instead</p><h3>What’s actually happening</h3><p><em>.gitignore</em> only works on files git is not already tracking</p><p>If you already committed the file before, git has it in its system already<br>So adding it to <em>.gitignore</em> after does basically nothing</p><p>It will keep tracking it like normal</p><p>That’s the part most people don’t realize early</p><h3>The fix</h3><p>You have to stop git from tracking it yourself</p><pre>git rm --cached .env</pre><p>That removes it from git, but not from your computer</p><p>Without <em>--cached </em>it deletes the file completely so don’t forget that</p><h3>Steps (just do this)</h3><p>1. Remove it:</p><pre>git rm --cached &lt;filename&gt;</pre><p>2. Add it to `.gitignore` if you haven’t:</p><pre>echo &quot;&lt;filename&gt;&quot; &gt;&gt; .gitignore</pre><p>3. Commit:</p><pre>git add .gitignore<br>git commit -m &quot;stop tracking &lt;filename&gt;&quot;</pre><p>4. Push it</p><p>that’s it</p><p>One more thing</p><p>If that file had API keys or secrets, they are already in your git history</p><p>Removing it now doesn’t remove it from older commits</p><p>So yeah… assume it’s exposed and change it</p><h3>Quick summary</h3><p><em>.gitignore </em>→ stops new files from being tracked<br><em>git rm --cached </em>→ stops already tracked file</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7be4e2b89a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hi, I’m Caleb. I’m Not Here to Drift.]]></title>
            <link>https://medium.com/@calchiwo/hey-im-caleb-chikanka-wodi-76963c5fc69a?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/76963c5fc69a</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 17:18:58 GMT</pubDate>
            <atom:updated>2026-04-26T09:56:53.528Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey, I’m Caleb Wodi.</p><p>I’m not trying to “pass time” or “figure things out slowly.” I’m building early, on purpose.</p><p>Most people my age are told to wait. Wait to grow up. Wait to start. Wait to be taken seriously.</p><p>I don’t buy that.</p><p>I think time is the only real leverage we get, and wasting it quietly is the easiest way to lose without noticing.</p><p>So I started building.</p><p>Not perfectly. Not with some master plan. Just consistently.</p><p>I launched Rocjet Technologies. I started working on WodiWideWeb.</p><p>And I was doing it all on a phone.</p><p>Reading and writing code on a small screen. Switching between apps. Managing files without real tooling. Slower. Harder. Limited.</p><p>But I kept showing up.</p><p>I was posting about it every day. Sharing the process. The progress. The friction. No shortcuts, no highlight-only version.</p><p>Day after day.</p><p>Eventually, people started paying attention.</p><p>They didn’t just notice. They stepped in.</p><p>With their help, and the support of a community that chose to believe in me, I got my first laptop through crowdfunding.</p><p>That moment matters more than I can fully explain.</p><p>Not just because of the laptop.</p><p>But because people I had never met decided that what I was building was worth backing.</p><p>Eduardo and Emmanuel didn’t just help me. They changed my trajectory.</p><p>I don’t take that lightly.</p><p>And I won’t waste it.</p><p>The laptop didn’t start the journey.</p><p>It removed friction from something that was already in motion.</p><p>Now I could build properly. Go deeper. Move faster. Think clearer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bfja2VSU2IZfyz58zkLkaQ.jpeg" /></figure><p>And that’s when I built ExplainThisRepo.</p><p>ExplainThisRepo is simple in idea, hard in execution.</p><p>It reads a codebase like a builder would. Not just summarizing files, but analyzing structure, entry points, configs, and dependencies to explain what the project actually does in plain English.</p><p>Because most people don’t struggle with code.</p><p>They struggle with understanding systems.</p><p>That’s the problem I’m solving.</p><p>To most people, these look like small projects.</p><p>To me, they’re not projects. They’re reps.</p><p>Each one is me learning how systems work. How ideas turn into something real. How structure beats motivation. How clarity beats noise.</p><p>I’m not chasing hype. I’m chasing understanding.</p><p>I don’t want to just “use” technology. I want to understand what’s underneath it. How code becomes behavior. How systems scale. How something small becomes something that matters.</p><p>That’s why I think differently about things like repos, websites, and even tweets.</p><p>A repo is not just code. It’s a foundation.</p><p>A website is not just a page. It’s an asset.</p><p>A tweet is not just a thought. It’s a signal.</p><p>Everything compounds if you treat it that way.</p><p>But there’s a reality I’m learning fast.</p><p>Starting is easy. Stacking ideas is easy. Feeling productive is easy.</p><p>What’s hard is focus.</p><p>What’s hard is finishing.</p><p>What’s hard is knowing what not to build.</p><p>I’ve felt that tension already. The urge to do everything at once. The temptation to move fast without direction. The risk of burning out before anything truly compounds.</p><p>So I’m learning to slow down without stopping.</p><p>To build fewer things, but build them properly.</p><p>To think in systems, not bursts.</p><p>To choose long-term clarity over short-term excitement.</p><p>I don’t have everything figured out. I’m not pretending to.</p><p>But I know this:</p><p>I’m not here to drift.</p><p>I’m here to build something that lasts.</p><p>And I’m starting now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*mntgExxb5QwotSv3r9mI9w.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76963c5fc69a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Today I added $10 more in Google shares, $8 in Oracle shares, $8 in Intel shares and $5 in Shopify…]]></title>
            <link>https://medium.com/@calchiwo/today-i-added-10-more-in-google-shares-8-in-oracle-shares-8-in-intel-shares-and-5-in-shopify-8206e50d8db3?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8206e50d8db3</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 14:27:35 GMT</pubDate>
            <atom:updated>2026-03-03T14:27:35.661Z</atom:updated>
            <content:encoded><![CDATA[<h3>Today I added $10 more in Google shares, $8 in Oracle shares, $8 in Intel shares and $5 in Shopify shares</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*iQg-ua3FHFiblGdbzlyYkg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*2VyqZIPFfpfNTTLzzEB_ww.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*UXI4F9YJfjZZxTUSlWShKA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*2gqaMtHpusEVDHSDMDw2DA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8206e50d8db3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I added more positions today]]></title>
            <link>https://medium.com/@calchiwo/i-added-more-positions-today-d8b3b7074278?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8b3b7074278</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 11:47:07 GMT</pubDate>
            <atom:updated>2026-03-02T11:47:07.141Z</atom:updated>
            <content:encoded><![CDATA[<p>I added more positions today</p><p>I invested $15 in S&amp;P 500, and bought $10 in Tesla shares and $8 in Meta shares</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*_2aiC4woYUq6VHwhxBjzhg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*g0R78Hht1aOww7ggs_AEeQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*wk-TTwrgMOJAz7DMOuosfg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8b3b7074278" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Continuing the long term game]]></title>
            <link>https://medium.com/@calchiwo/continuing-the-long-term-game-348035dc1e85?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/348035dc1e85</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 11:45:37 GMT</pubDate>
            <atom:updated>2026-03-02T11:45:37.806Z</atom:updated>
            <content:encoded><![CDATA[<p>Continuing the long term game</p><p>I invested $10 in NVDA shares, $7 in AMZN shares and $7 in MSFT shares today</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*RyspfH6hMoQHrY_SE_Y-Eg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*IN1tixABBqtWhlkXkjsQAQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*353Fjy6OKlodxuWUN5amYQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=348035dc1e85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[As part of me playing the long term game]]></title>
            <link>https://medium.com/@calchiwo/as-part-of-me-playing-the-long-term-game-a04eecb84559?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a04eecb84559</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Sat, 21 Feb 2026 15:04:40 GMT</pubDate>
            <atom:updated>2026-02-21T15:04:40.714Z</atom:updated>
            <content:encoded><![CDATA[<p>As part of me playing the long term game</p><p>I started investing in stocks today</p><p>I bought $5 in GOOG shares, $10 in AAPL shares and $6 in Reddit shares</p><p>At today’s rate, that is roughly ₦25,000 total</p><p>Crypto taught me speed. Stocks will teach patience</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*p_a1sDBH7F8-gnSSfMkx5g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*76zWmUA4AWtxfiMTjgG7zA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*PTg_4U994c0-kkIMy5uBBA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a04eecb84559" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I coded my first colored ASCII art in Python today.]]></title>
            <link>https://medium.com/@calchiwo/i-coded-my-first-colored-ascii-art-in-python-today-28248419d158?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/28248419d158</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Sun, 07 Dec 2025 20:30:52 GMT</pubDate>
            <atom:updated>2025-12-07T20:30:52.506Z</atom:updated>
            <content:encoded><![CDATA[<p>I coded my first colored ASCII art in Python today.</p><p>Spent time setting up the environment and figuring out why the script refused to run.<br>I fixed a missing module error and got the script working.<br>It took time, but patience paid off.</p><p>I did everything on my phone, the same screen where this journey started</p><p>Another small win 💪<br>#Python</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*xGUOUIY9F0Edx-JE3FPYpQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28248419d158" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I built a multiplication table in Python using only my phone.]]></title>
            <link>https://medium.com/@calchiwo/i-built-a-multiplication-table-in-python-using-only-my-phone-3797f2f0a8f2?source=rss-e9c05a661b7f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3797f2f0a8f2</guid>
            <dc:creator><![CDATA[Caleb Wodi]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 16:25:46 GMT</pubDate>
            <atom:updated>2025-12-04T16:25:46.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*8w3Gd-NovVj2T8xEW88qOg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Q6t8NYHd6mOO6AF_tnXM6g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3797f2f0a8f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>