<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bensidney Ndungu</title>
    <description>The latest articles on DEV Community by Bensidney Ndungu (@codewithsidney).</description>
    <link>https://dev.to/codewithsidney</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3786931%2F938c8021-c0b2-4d31-9f5f-eab1281fe357.png</url>
      <title>DEV Community: Bensidney Ndungu</title>
      <link>https://dev.to/codewithsidney</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/codewithsidney"/>
    <language>en</language>
    <item>
      <title>I Fell for Someone I'd Never Heard Of. Her Name Is Visatile.</title>
      <dc:creator>Bensidney Ndungu</dc:creator>
      <pubDate>Thu, 19 Nov 2026 11:37:35 +0000</pubDate>
      <link>https://dev.to/codewithsidney/i-fell-for-someone-id-never-heard-of-her-name-is-visatile-1em1</link>
      <guid>https://dev.to/codewithsidney/i-fell-for-someone-id-never-heard-of-her-name-is-visatile-1em1</guid>
      <description>&lt;p&gt;Three months ago, I met someone I had never heard of.&lt;/p&gt;

&lt;p&gt;I wasn't looking. I was a final-year software engineering student, applying for anything with "developer" in the title. Then she showed up: complicated, ambitious, and somehow everywhere at once. Kenya. Uganda. Zanzibar. Now Rwanda.&lt;/p&gt;

&lt;p&gt;Her name is &lt;strong&gt;Visatile&lt;/strong&gt;. And yes, my friends think she's only entertaining me for the money.&lt;/p&gt;

&lt;p&gt;Let me tell you about her.&lt;/p&gt;




&lt;h2&gt;
  
  
  How we met
&lt;/h2&gt;

&lt;p&gt;It started the way most developer love stories do: with an application, a few nervous calls, and a first day spent staring at a codebase much bigger than anything I had built at university.&lt;/p&gt;

&lt;p&gt;Visatile is an experiences marketplace for East Africa. Travellers book safaris, boat rides, cooking classes and cultural tours, hosted by the locals who actually run them. I joined as a &lt;strong&gt;software engineer&lt;/strong&gt;, and within a week I realised she was a lot more than a booking website.&lt;/p&gt;

&lt;h2&gt;
  
  
  First impressions: she's complicated
&lt;/h2&gt;

&lt;p&gt;On the surface, it's simple: you pick an experience, you book, you go.&lt;/p&gt;

&lt;p&gt;Underneath, a lot is going on. There are listings with their own prices, dates and photos. There are travellers paying from different countries, hosts who need to be paid, and messages, reviews and support holding it all together.&lt;/p&gt;

&lt;p&gt;My first few weeks were mostly reading. Reading code, reading pull requests, reading old commit messages like letters from someone's past. Slowly, the pieces started to make sense.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 2am conversations
&lt;/h2&gt;

&lt;p&gt;Every relationship has its late nights. Ours usually start with something that works perfectly on my machine and nowhere else.&lt;/p&gt;

&lt;p&gt;I've learned to love those moments, mostly in hindsight. A date that shows up a day early because of a time zone. A page that's fast on Wi-Fi and painfully slow on mobile data. A form that works in English and gets confused by a name with an apostrophe.&lt;/p&gt;

&lt;p&gt;Each one taught me the same thing: the bug is rarely where you first look. Read the logs, reproduce it, write it down, and only then touch the code.&lt;/p&gt;

&lt;h2&gt;
  
  
  Getting to know her people
&lt;/h2&gt;

&lt;p&gt;She sends me photos. Mostly of elephants.&lt;/p&gt;

&lt;p&gt;She also knows people everywhere: guides in the Mara, boat captains on the coast, mamas who teach visitors to cook pilau, artisans who shape clay by hand. Many of them run their whole business from a phone.&lt;/p&gt;

&lt;p&gt;Building for them changes how you think:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Phones come first.&lt;/strong&gt; If it doesn't work well on a mid-range Android on mobile data, it doesn't work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simple beats clever.&lt;/strong&gt; A host should be able to understand a screen without a tutorial.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trust is everything.&lt;/strong&gt; People are trusting the platform with their income, and that deserves care.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The red flag that wasn't
&lt;/h2&gt;

&lt;p&gt;My friends' theory: she's only in it for the money.&lt;/p&gt;

&lt;p&gt;Here's the plot twist. On every booking, &lt;strong&gt;Visatile keeps just 10%. The other 90% goes to the local host&lt;/strong&gt;, the mwananchi wa kawaida who actually makes the experience happen.&lt;/p&gt;

&lt;p&gt;Many booking platforms keep a much bigger share, and much of it leaves the local economy. Visatile was built so that tourism money stays with the people who earn it. Once I understood that, the code stopped feeling like tickets and started feeling like something that matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  I'm still learning (and I hope I never stop)
&lt;/h2&gt;

&lt;p&gt;If these three months have taught me anything, it's how much I don't know yet.&lt;/p&gt;

&lt;p&gt;Every week brings something new: a pattern I hadn't seen before, a better way to name things, a review comment that changes how I think about a problem. Some days I feel like I'm finally getting it. The next day, the codebase humbles me again.&lt;/p&gt;

&lt;p&gt;Honestly, I don't think the learning will stop any time soon, and I don't want it to. That's the best part of this job.&lt;/p&gt;

&lt;h2&gt;
  
  
  To the team
&lt;/h2&gt;

&lt;p&gt;None of this happens alone.&lt;/p&gt;

&lt;p&gt;To the Visatile team: thank you for the patience, the code reviews, the "have you tried…" messages, and for trusting a new engineer with real work. And thank you for building something that puts local hosts first. What you're doing for travellers and for mwananchi wa kawaida across East Africa is genuinely impressive, and I'm proud to be a small part of it. &lt;/p&gt;

&lt;h2&gt;
  
  
  Meet her
&lt;/h2&gt;

&lt;p&gt;I made a carousel about this whole "relationship". Here's how it ends:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi3yozt4o06zu91jeaxyc.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi3yozt4o06zu91jeaxyc.jpg" alt="This is her: Stampy, the Visatile mascot" width="800" height="1000"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That's &lt;strong&gt;Stampy&lt;/strong&gt;, Visatile's mascot, standing in for every local guide and host on the platform.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; Book an experience or become a host: &lt;a href="http://visatile.com" rel="noopener noreferrer"&gt;Visatile&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt; Connect with me: &lt;a href="https://www.linkedin.com/in/bensidney-ndung-u/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And now I want to hear yours: &lt;strong&gt;what's the codebase you fell for?&lt;/strong&gt; 👇&lt;/p&gt;

</description>
      <category>career</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>africa</category>
    </item>
    <item>
      <title>Getting Started with Microsoft Copilot as a Developer</title>
      <dc:creator>Bensidney Ndungu</dc:creator>
      <pubDate>Thu, 05 Mar 2026 11:47:59 +0000</pubDate>
      <link>https://dev.to/codewithsidney/getting-started-with-microsoft-copilot-as-a-developer-29f5</link>
      <guid>https://dev.to/codewithsidney/getting-started-with-microsoft-copilot-as-a-developer-29f5</guid>
      <description>&lt;p&gt;As developers, we're always looking for ways to work faster and smarter. Recently, I started experimenting with Microsoft Copilot, and it completely changed how I approach some everyday development tasks.&lt;/p&gt;

&lt;p&gt;AI tools are no longer just experiments—they are becoming part of the modern developer workflow.&lt;/p&gt;

&lt;p&gt;What is Microsoft Copilot?&lt;/p&gt;

&lt;p&gt;Microsoft Copilot is an AI assistant that helps developers and professionals complete tasks faster by generating suggestions, answering questions, and assisting with workflows.&lt;/p&gt;

&lt;p&gt;If you're curious about how it works, you can explore it here:&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://learn.microsoft.com/copilot/?wt.mc_id=studentamb_504278" rel="noopener noreferrer"&gt;https://learn.microsoft.com/copilot/?wt.mc_id=studentamb_504278&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Things that surprised me&lt;/p&gt;

&lt;p&gt;After trying it out, here are a few things that stood out:&lt;/p&gt;

&lt;p&gt;1️⃣ Faster code generation&lt;/p&gt;

&lt;p&gt;Copilot can help generate code snippets quickly, which is useful when working with repetitive patterns.&lt;/p&gt;

&lt;p&gt;2️⃣ Documentation assistance&lt;/p&gt;

&lt;p&gt;Writing documentation is often overlooked, but Copilot can help generate explanations and comments for your functions.&lt;/p&gt;

&lt;p&gt;3️⃣ Research without leaving your workflow&lt;/p&gt;

&lt;p&gt;Instead of constantly searching documentation, AI tools can help summarize APIs and concepts while you work.&lt;/p&gt;

&lt;p&gt;Why this matters for developers&lt;/p&gt;

&lt;p&gt;AI-assisted development doesn't replace developers—it augments productivity. It allows us to focus more on solving problems and less on repetitive tasks.&lt;/p&gt;

&lt;p&gt;As AI tools improve, they may become a standard part of the developer toolkit.&lt;/p&gt;

&lt;p&gt;What do you think?&lt;/p&gt;

&lt;p&gt;Have you experimented with AI tools like Copilot in your development workflow?&lt;/p&gt;

&lt;p&gt;Do you think AI will become a normal part of coding in the next few years?&lt;/p&gt;

&lt;p&gt;I'd love to hear your thoughts.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>githubcopilot</category>
      <category>productivity</category>
      <category>developers</category>
    </item>
    <item>
      <title>Understanding Microservices Architecture on Azure as a Node.js Developer</title>
      <dc:creator>Bensidney Ndungu</dc:creator>
      <pubDate>Mon, 23 Feb 2026 16:00:32 +0000</pubDate>
      <link>https://dev.to/codewithsidney/understanding-microservices-architecture-on-azure-as-a-nodejs-developer-3oa3</link>
      <guid>https://dev.to/codewithsidney/understanding-microservices-architecture-on-azure-as-a-nodejs-developer-3oa3</guid>
      <description>&lt;p&gt;As a developer working with Node.js and Express, I’ve been diving into cloud-native architectures to build scalable and resilient systems. One concept that stood out is microservices.&lt;/p&gt;

&lt;p&gt;Microservices allow you to break your application into independent services that can be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deployed individually&lt;/li&gt;
&lt;li&gt;Scaled independently&lt;/li&gt;
&lt;li&gt;Managed with better fault isolation&lt;/li&gt;
&lt;li&gt;Updated without affecting the whole system&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;While building my projects, I realized how much easier Azure makes this. Microsoft provides a clear guide to designing microservices on Azure, which explains patterns like API Gateway, service discovery, and container orchestration.&lt;/p&gt;

&lt;p&gt;Check it out here:&lt;br&gt;
👉 &lt;a href="https://learn.microsoft.com/en-us/azure/architecture/guide/architecture-styles/microservices?wt.mc_id=studentamb_504278" rel="noopener noreferrer"&gt;Microsoft Azure Microservices Guide&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Key takeaways for developers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Start small — build one service, then scale&lt;/li&gt;
&lt;li&gt;Use Azure container services for orchestration&lt;/li&gt;
&lt;li&gt;Implement monitoring early to catch failures&lt;/li&gt;
&lt;li&gt;Automate deployments for faster iteration&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I’d love to hear from other developers: how are you structuring your apps? Are you using microservices, monoliths, or something in between? Let’s discuss in the comments!&lt;/p&gt;

</description>
      <category>azure</category>
      <category>microservices</category>
      <category>node</category>
      <category>studentambassador</category>
    </item>
  </channel>
</rss>
