<?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 Youmbi Leo on Medium]]></title>
        <description><![CDATA[Stories by Youmbi Leo on Medium]]></description>
        <link>https://medium.com/@yll0rd?source=rss-0cdf43c44cd8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lyGB61li8v8ERt2DFoEdwA.jpeg</url>
            <title>Stories by Youmbi Leo on Medium</title>
            <link>https://medium.com/@yll0rd?source=rss-0cdf43c44cd8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:50:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yll0rd/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[Stuck on Mount Stupid: How AI tricks Us into Thinking We’re Experts | Youmbi Leo]]></title>
            <link>https://medium.com/@yll0rd/stuck-on-mount-stupid-how-ai-tricks-us-into-thinking-were-experts-youmbi-leo-4ba9caffa3f6?source=rss-0cdf43c44cd8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ba9caffa3f6</guid>
            <dc:creator><![CDATA[Youmbi Leo]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 21:27:49 GMT</pubDate>
            <atom:updated>2026-10-02T12:42:53.867Z</atom:updated>
            <content:encoded><![CDATA[<h3>Personally…</h3><p>I recently had the privilege of being one of the few shortlisted and called for a technical interview in a big tech company in my country. We were given a couple of “tagged-easy” DSA problems to solve, but trust me, they were everything but easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/761/0*DYIzlvRi4yNJqIY5.png" /></figure><p>And it seemed to me as we all (the candidates) shared the same difficult experience. <br>I believed that since I had experience building <a href="https://github.com/yll0rd/?tab=repositories">projects</a>, mostly using an AI harness, everything should have gone well. I over-estimated my capabilities/competence in DSA problems solving. And this, my dear reader, is the symptom of the <strong>Dunning-Kruger Effect</strong>.</p><h3>Understanding the Dunning-Kruger Effect</h3><p>A formal definition would be: <strong>a whereby people with limited knowledge or competence in a given intellectual or social domain greatly overestimate their own knowledge or competence in that domain</strong>.</p><p>In layman’s terms, <strong>it is when someone with low ability in a particular area overestimate his/her competence</strong>. It is not necessarily arrogance; it is about not knowing what you don’t know.</p><p>You are surely familiar with the concept: <a href="https://www.britannica.com/topic/imposter-syndrome#ref1"><strong>Imposter’s Syndrome</strong></a>Well, it ‘can’ be considered the opposite of the D-K effect.</p><h3>The Illusion of Competence</h3><p>Knowledge has become so accessible nowadays with the advent of AI. Just a single “What is ..” search and the <strong>AI mode</strong> brings out a <strong>full summary</strong> of the topic. The drawback of this is that people, not only take this as the absolute truth, but also, do not realize how shallow that knowledge actually is.</p><p>Imagine someone — let’s call him <em>Steven</em> — wants to understand the economics of inflation and deflation. Instead of reading a textbook or studying market dynamics, he asks an AI tool for a quick explanation. The AI gives him a neat, 3-bullet answer: it defines the terms, attributes inflation to supply and demand imbalances, and notes that central banks adjust interest rates to fix it. Steven walks away feeling like an expert. Armed with this “deemed-deep” knowledge, he jumps into debates with actual economists, confidently spouting oversimplified answers to incredibly complex financial problems. <em>I know we all have a Steven in our lives… and thanks to instant AI summaries, it’s easier than ever to accidentally become one.</em></p><h3>The Crutch Effect</h3><p>This superficial understanding is creating a bigger issue: we are neglecting actual skill acquisition and coming to rely almost entirely on AI to do the heavy lifting. For instance,<em> a marketing director might rely on AI to generate flawless campaign strategies, yet lack the real-world intuition to diagnose why a failing ad isn’t converting. Similarly, a developer can use AI to auto-generate code, but when a complex bug hits production, they struggle to debug it because they never mastered the underlying logic.</em><br>An esteemed senior of mine, <a href="https://www.linkedin.com/in/delia-ayoko">Ms. Delia Ayoko</a>, back at the Google DevFest 2024, gave a <a href="https://www.linkedin.com/posts/delia-ayoko_last-saturday-was-devfest-season-for-the-ugcPost-7267989160169242625-92gg/">talk</a> titled “ <strong>Human Overdependence on AI</strong> “. A key insight I took away was that real learning happens at the human level: it’s through actually putting in the work and pushing through the struggle that our brain creates new neural connections, building genuine competence that no AI tool can replicate.</p><h3>The D-K Curve</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/0*v96BFRkW9JfK3mIe.png" /></figure><p>This curve best shows the difference between perceived ability and actual ability. The Dunning-Kruger curve illustrates this psychological trap. Beginners start at the “ <strong>Peak of Mount Stupid</strong>” or the “ <strong>I know everything</strong>” stage where minimal knowledge produces maximum confidence. As they learn more, they plunge into the “ <strong>Valley of Despair</strong> “ realizing how vastly complex the domain actually is.</p><p>AI creates a shortcut straight to the peak. By supplying quick answers, it lets users bypass the initial learning friction, giving them peak confidence without ever pushing them down the curve toward actual understanding. Real mastery requires pushing through the valley, confronting what you don’t know, and slowly climbing the slope of enlightenment through deliberate practice and hands-on trial and error.</p><h3>Final Thoughts</h3><p>Please, don’t misunderstand me: I am not condemning the use of AI. It remains an extraordinary tool for productivity and learning when used intentionally. However, we must treat it as a stepping stone rather than a replacement for deep thinking. Real expertise requires intellectual humility. As <strong>Socrates</strong> famously observed, “ <strong>The only true wisdom is in knowing you know nothing.</strong> “ By acknowledging the limits of our knowledge, we can leverage AI to accelerate our growth without falling into the trap of superficial competence.</p><p><em>Originally published at </em><a href="https://yll0rd.me/writing/stuck-on-mount-stupid-how-ai-tricks-into-thinking-we-re-experts"><em>https://yll0rd.me</em></a><em> on October 1, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ba9caffa3f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Slacking your .env files (Please, I am begging you)]]></title>
            <link>https://medium.com/@yll0rd/stop-slacking-your-env-files-please-i-am-begging-you-d25a3ba27acc?source=rss-0cdf43c44cd8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d25a3ba27acc</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[user-onboarding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Youmbi Leo]]></dc:creator>
            <pubDate>Mon, 08 Dec 2025 20:41:18 GMT</pubDate>
            <atom:updated>2025-12-08T20:41:18.573Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stop Slacking your .env files (Please, I am begging you)</h3><p>You know that moment when a new dev joins your team and asks,</p><blockquote>“Hey, where do I get the API keys?”</blockquote><p>And you’re like… 😬</p><p>Do you:<br>a) Slack them the <em>.env</em> file (please no 🤲🏽)<br>b) Email it (even worse 🙅🏾‍♂️)<br>c) Put it in a Google Doc (are you trying to get fired?)<br>d) Awkwardly screen share and watch them frantically type (the slow death)<br>e) Actually use a proper tool like a professional human being</p><p>If you picked anything other than E, we need to talk.</p><h3>The .env Problem We All Pretend Doesn’t Exist</h3><p>Let’s be real for a second. Environment variables are like the secret sauce of your application. They’ve got:</p><ul><li>Database passwords that would make your DB Admin cry if leaked</li><li>API keys worth more than your coffee budget</li><li>Secret tokens that unlock the gates to production</li><li>OAuth credentials that are definitely not meant for GitHub</li></ul><p>And yet… we’re out here treating them like they’re public information.</p><p><strong>The Classic Developer Horror Stories:</strong></p><p>🚨 “I accidentally committed my AWS keys to GitHub and now I owe $50,000”<br>🚨 “Someone left the company and we don’t know what environment variables they changed”<br>🚨 “Works on my machine… oh wait, you’re missing 15 env vars”<br>🚨 “Who changed <em>DATABASE_URL</em> last week and why is production down?”</p><p>Sound familiar? Yeah, we’ve all been there.</p><h3>Enter Nvii: Git for Your Secrets (But Actually Secure)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FqpT1V4SgVe6ar_nt02IHA.png" /></figure><p><a href="https://nvii.dev/"><strong>Nvii</strong></a> is basically what happens when someone finally said, “You know what? Environment variables deserve the same love we give our code.”</p><p>Think about it:</p><ul><li>Your code gets Git (version control, history, branches, rollback)</li><li>Your<em> .env</em> files get… Slack messages? Miserable!!</li></ul><p><strong>Nvii gives your environment variables:</strong><br>✅ Version control (like Git)<br>✅ Push/pull workflows (like Git) <br>✅ Branch management (like Git)<br>✅ History and rollback (like Git)</p><p>It’s like Git and a vault had a baby, and that baby is really good at keeping secrets.</p><h3><strong>Show Me The Code!</strong></h3><p>Alright, enough theory. Let’s get our hands dirty.</p><h4>Installation</h4><pre># Global install (because you&#39;ll use this everywhere)<br>npm install -g nvii<br><br># Linux users, you know the drill<br>sudo npm install -g nvii</pre><h4>First Time Setup (The “This is Amazing” Moment)</h4><pre># Step 1: Login (opens browser, super smooth)<br>nvii login<br><br># Step 2: Create your first project<br>nvii new<br># This reads your existing .env file<br># You give it a name like &quot;my-awesome-api&quot;<br># Boom - encrypted and uploaded<br><br># Step 3: Make a change to your .env file<br>echo &quot;NEW_FEATURE_FLAG=true&quot; &gt;&gt; .env<br><br># Step 4: Push it up (with a message, like Git commits)<br>nvii push -m &quot;Added feature flag for new dashboard&quot;<br><br># Step 5: Check the history (because you&#39;re paranoid, and that&#39;s healthy)<br>nvii log</pre><p><strong>On Your Teammate’s Machine (The “Onboarding is Easy Now” Moment)</strong></p><pre># They login<br>nvii login<br><br># They link to your project<br>nvii link<br># Interactive menu shows them all projects they have access to<br># They pick &quot;my-awesome-api&quot;<br><br># They pull the env vars<br>nvii pull<br># BAM! They have a working .env file<br># No Slack messages, no screenshots, no tears</pre><h3>Real-World Workflows</h3><h4>The Multi-Environment Setup</h4><p>You know how you have dev, staging, and production? Different configs for each? Nvii’s got branches for that.</p><pre># Create a staging branch<br>nvii branch --name staging<br><br># Switch to it<br>nvii checkout --name staging<br><br># Push your staging configs<br>nvii push --message &quot;Staging environment setup&quot;<br><br># Switch back to main (production)<br>nvii checkout --name main</pre><p>Now your environments are properly separated, versioned, and impossible to accidentally mix up at 3 AM.</p><h4>The “Oh No, We Broke Production” Workflow</h4><pre># View your history<br>nvii log --oneline<br><br># Output:<br># abc123 2024-12-08 john@company.com &quot;Updated API keys&quot;<br># def456 2024-12-07 jane@company.com &quot;Changed database URL&quot;<br># ghi789 2024-12-06 john@company.com &quot;Initial setup&quot;<br><br># Oops, that API key update broke everything<br># Rollback to the previous version<br>nvii rollback --version def456<br><br># Crisis averted. Production is happy. You&#39;re a hero.</pre><h4>The “New Dev Onboarding” Workflow</h4><p><strong>Before Nvii:<br></strong>- 2 hours of setup<br>- 47 Slack messages<br>- 3 <em>“it still doesn’t work”</em> escalations<br>- 1 existential crisis</p><p><strong>After Nvii:</strong></p><pre>nvii login<br>nvii link<br>nvii pull<br>npm run dev  # It just works™</pre><p><strong>Time saved:</strong> Your entire afternoon<br><strong>Sanity preserved:</strong> Immeasurable</p><h3>The Web Dashboard (For The Clicky People)</h3><p>Not everyone loves the terminal (we know, shocking). Nvii has a web dashboard at <a href="https://nvii.dev/">https://nvii.dev</a> where you can:</p><ul><li>View all your projects</li><li>See version history with a pretty UI</li><li>Manage team access</li><li>Edit environment variables (with encryption, obviously)</li><li>Invite team members</li><li>View audit logs</li></ul><p>It’s like GitHub, but for your environment variables.</p><h3>Resources</h3><p>📚 <strong>Documentation: </strong><a href="https://docs.nvii.dev/">https://docs.nvii.dev</a><br>🐙 <strong>GitHub</strong>: <a href="https://github.com/skaleway/nvii">https://github.com/skaleway/nvii</a><br>💬 <strong>Issues/Questions</strong>: <a href="https://github.com/skaleway/nvii/issues">https://github.com/skaleway/nvii/issues</a></p><p>Now go forth and stop Slacking your <em>.env</em> files. Your security team will thank you. Your new hires will thank you. Your future self will thank you.</p><p>And if you save just ONE person from committing AWS keys to GitHub, you’ve made the internet a better place. 🌟</p><p><strong>P.S. If you’re still Slacking <em>.env</em> files after reading this, we can’t be friends anymore. Sorry, I don’t make the rules.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d25a3ba27acc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when you type google.com in your browser and press Enter]]></title>
            <link>https://medium.com/@yll0rd/what-happens-when-you-type-google-com-in-your-browser-and-press-enter-6df242665da5?source=rss-0cdf43c44cd8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6df242665da5</guid>
            <category><![CDATA[dns-servers]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[servers]]></category>
            <dc:creator><![CDATA[Youmbi Leo]]></dc:creator>
            <pubDate>Sat, 14 Oct 2023 20:52:37 GMT</pubDate>
            <atom:updated>2023-10-14T20:52:37.203Z</atom:updated>
            <content:encoded><![CDATA[<p>When you type <a href="https://www.google.com/">https://www.google.com</a> in your browser and press Enter, several processes are set in motion to ensure that you are able to access the website. The first step is a DNS request, where your computer sends a query to a Domain Name System (DNS) server to translate the URL into an IP address. This IP address is necessary for your computer to know which server to connect to.</p><p>Once the DNS request is completed, the next step is establishing a TCP/IP connection. This involves a series of handshakes between your computer and the server to ensure a stable and secure connection. If the connection is successful, the firewall on the server will then check for any potential threats and block them if necessary.</p><p>The next important aspect of accessing <a href="https://www.google.com/">https://www.google.com</a> is HTTPS/SSL. This stands for Hypertext Transfer Protocol Secure and Secure Sockets Layer, respectively. These protocols ensure that the data being transmitted between your computer and the server is encrypted and cannot be intercepted by any third party.</p><p>Once the connection is secure, your request is then routed to a load-balancer. This is a server that distributes the incoming traffic to multiple web servers to ensure efficient and balanced use of resources. From there, your request is sent to a web server, which is responsible for delivering the content of the website to your browser.</p><p>The website itself is hosted on an application server, which is responsible for executing any necessary code and generating dynamic content. This could include search results, images, maps, and other features on the website. The application server also connects to a database, which stores and retrieves any necessary information for the website.</p><p>In summary, when you type <a href="https://www.google.com/">https://www.google.com</a> in your browser, a series of complex processes take place to ensure that you are able to access the website securely and efficiently. From translating the URL to establishing a secure connection to delivering the website’s content, a lot goes on behind the scenes to make your browsing experience seamless.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6df242665da5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>