<?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 Julie Sau on Medium]]></title>
        <description><![CDATA[Stories by Julie Sau on Medium]]></description>
        <link>https://medium.com/@julienyange?source=rss-1c78e074bf8a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ern3ykIOKtUJD6TYJSiNcw.jpeg</url>
            <title>Stories by Julie Sau on Medium</title>
            <link>https://medium.com/@julienyange?source=rss-1c78e074bf8a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 06:42:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@julienyange/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[Introducing Rentall Scale: Your Ticket to Adventure!]]></title>
            <link>https://medium.com/@julienyange/introducing-rentall-scale-your-ticket-to-adventure-3fa694d32b73?source=rss-1c78e074bf8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fa694d32b73</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[bus-booking-software]]></category>
            <category><![CDATA[portfolio-project]]></category>
            <category><![CDATA[alx-blog]]></category>
            <dc:creator><![CDATA[Julie Sau]]></dc:creator>
            <pubDate>Wed, 15 May 2024 20:47:17 GMT</pubDate>
            <atom:updated>2024-05-15T20:47:17.403Z</atom:updated>
            <content:encoded><![CDATA[<h3>Effortlessly Plan, Book, and Manage Your Bus Trips</h3><p>One of the most common scenes in Nairobi CBD at 5pm is the human traffic, vehicle traffic and absolute chaos that is the transportation industry during rush hours. The tiring and never-ending long queues from Khoja to Railways, spending hours on end, just waiting for the chance to catch a ride home, only for you to fight to get into the bus, despite having queued for THAT long. Does that sound familiar? Too familiar infact.</p><p>This experience is what gave rise to Rentall Scale Bookings. An application that makes planning for future trips by enabling secure bookings, seamless payment methods. Now you’re able to secure your seat in advance to beat the rush. No more fighting to get a seat in the bus and no more waiting for countless hours. Whether you’re a daily commuter or a weekend wanderer, Rentall Scale is here for you. We’re all about making bus travel a breeze for everyone.</p><p>Alright, here’s the scoop — buses have been a big part of my life since day one. Growing up in a tiny town where buses were our lifeline, I’ve had some epic adventures on those wheels. From visiting relatives to exploring new places, buses were my ticket to excitement. And now, working on BusEase, I’m on a mission to spread that joy of travel to everyone!</p><p><strong>3. Project Summary</strong></p><p>Architecture:</p><p>Tech Talk: We’re rocking Flutter for the frontend, Node.js with Express.js for the backend, MongoDB for the database, and Stripe for payments. Plus, we’ve got Google Maps API for mapping magic.</p><p>What We’ve Cooked Up:</p><ol><li>Signin made simple. Create an account by signing in with Google or Facebook.</li><li>View active bus routes and schedules.</li><li>Book bus rides for you and your friends or family members.</li><li>View history of trips and upcoming trips.</li><li>Seamless payment using Lipa na Mpesa.</li></ol><p><strong>4. Tech Challenge</strong></p><p>The biggest challenge was being able to host the architecture. Building with scalability in mind, the app ended up having quite a number of services that required hosting either on kubernetes or on a platform that would make the whole process painless. Luckily we were able to stumble upon a platform that served all our needs without exercising expertise beyond our means.</p><p><strong>5. Lessons Learned</strong></p><p>This wild ride called Rentall Scale taught me some valuable lessons — like the power of teamwork, the magic of problem-solving, and the importance of keeping the fun alive. It’s been a blast, and I can’t wait to see where the journey takes us next!</p><p><strong>About Me</strong></p><p>Hey, I’m Juliana Sau, the brains behind the blog and a passionate software wizard. When I’m not crafting code or designing dreams, you’ll find me soaking up sunshine, sipping coffee, and dreaming up the next big thing. Come say hi on <a href="https://www.linkedin.com/in/juliana-sau/">LinkedIn</a> and join me on this wild ride!</p><p>So there you have it — the inside scoop on Rentall Scale, straight from the heart. Check out our <a href="https://bookings.rentallscale.com/">website</a> and <a href="https://www.linkedin.com/company/rentall-scale">LinkedIn</a> pages to learn more.</p><p>Stay tuned for more adventures and updates coming your way. Until next time, happy travels, friends! 🚌✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fa694d32b73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Incident Report: The Case of the Missing Environment Variable]]></title>
            <link>https://medium.com/@julienyange/incident-report-the-case-of-the-missing-environment-variable-a7f5bf1ed63f?source=rss-1c78e074bf8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7f5bf1ed63f</guid>
            <category><![CDATA[alxafrica]]></category>
            <category><![CDATA[postmortem-report]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Julie Sau]]></dc:creator>
            <pubDate>Sun, 14 Apr 2024 11:17:32 GMT</pubDate>
            <atom:updated>2024-04-14T11:17:32.084Z</atom:updated>
            <content:encoded><![CDATA[<p>In this short story, I shall chronicle a snapshot of my very first experiences in the world of devops and development, and rookie mistakes you can have a laugh about later in life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*6Px52uhvE7vNnTmm.jpg" /></figure><p>There comes a time in a young developer’s life when you have to learn more than you signed up for on the job, become a jack of all trades if you will. Crafting personal and professional projects comes with the responsibility of gaining some knowledge in a different area of expertise just to get your project up and running.</p><p>In this fateful phase of my life, it seemed learning devops was the next step to take. I spent the next couple of weeks learning a bit of it, failing terribly at deploying something a couple of times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qlkki5uyT5o-17sE.jpg" /><figcaption>Me reading the docs trying to find where I went wrong</figcaption></figure><p>After meticulously developing a feature for my current project, I was ready for it to see the light of day. Being new to continuous integration and continuous deployment (CI/CD) automation, I had setup a deployment pipeline for my project using hefty tutorials and documentations online and was sure it was watertight. Setting up simple GitHub workflow tests to ensure that builds were passing, and no type errors made it to production. <em>“I run a very tight ship”</em>, I thought to myself.</p><p>And that there was the beginning of the rookie mistake. I excitedly began the process to ship my code through the pipeline, confident that this feature would definitely be received well. Once my pull request was made, time to wait on my handy GitHub workflow (that VERY simple one I wrote) to confirm that everything was working fine. Those green checks always make my day. With all tests green and the code up to date, its time to ship the feature.</p><p>Just as a routine check, I tested the feature to ensure its working fine. To my shock, the feature isn’t working. The first sensical thing to do is check the code running on localhost. Everything is working as expected.</p><blockquote><em>“But it works on my machine”</em> says Every. Developer. Ever.</blockquote><p>Fast forward to me several hours later trying to pinpoint where exactly the problem is coming from.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/0*6e2DfC8KDDSIzZFR.jpg" /><figcaption>Me trying to explain how the code is working on my machine but not in prod</figcaption></figure><p>After being frustrated for a while, I decided to take a walk, touch some grass, as one does, to unwind and kind of get my head straight before diving back in to get to the root cause of problem.</p><p>Once I felt I was refreshed, I decided to start from the basics. They say as a developer, <em>console.log()</em> is your best friend. I logged every possible thing that could I felt could be the problem.</p><p>In a moment of clarity, I took a long shot and decided to log the environment variable to see what value it was passing, only to realize the true nature of my folly — a humble environment variable, forgotten amidst the chaos of deployments and configurations. With a mixture of relief and embarrassment, I swiftly rectified my oversight, setting the missing variable in its rightful place.</p><p>And lo and behold, the feature started working as perfectly as it was designed. All that fuss, just to find out how small the problem was! The only thing you can do in that moment is just laugh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0mNgDgcsTLTCuQTp" /><figcaption>Me pretending to be “shocked” when the deployment finally works!</figcaption></figure><p>I emerged from the ordeal with a newfound appreciation for the intricacies of devops, a healthy dose of humility, and a resolve to always double-check my environment variables before embarking on future deployments😂</p><p>So, dear reader, let this tale serve as a cautionary reminder — in the world of software development, even the most trivial of oversights can lead to monumental mishaps. But with determination, a dash of humor, and a willingness to learn from our mistakes, we can turn even the most disastrous of incidents into valuable lessons learned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7f5bf1ed63f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surfing the Web: A Guide to the Digital Odyssey]]></title>
            <link>https://medium.com/@julienyange/surfing-the-web-a-guide-to-the-digital-odyssey-0346469cb453?source=rss-1c78e074bf8a------2</link>
            <guid isPermaLink="false">https://medium.com/p/0346469cb453</guid>
            <category><![CDATA[surfing-the-web]]></category>
            <category><![CDATA[how-the-internet-works]]></category>
            <category><![CDATA[lax]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Julie Sau]]></dc:creator>
            <pubDate>Sun, 17 Mar 2024 17:52:36 GMT</pubDate>
            <atom:updated>2024-03-17T17:52:36.244Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey there, fellow digital adventurers! Have you ever wondered what happens behind the scenes when you type <a href="https://www.google.com/"><em>“www.google.com”</em></a> on your browser and press Enter?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*ZktKFMDPsDrjq9jvMMGs7w.jpeg" /></figure><h3>Introduction:</h3><p>As we navigate the vast sea of information that is the internet, clicking through websites with ease, we seldom stop to ponder the intricate dance of technologies that enables this seamless experience. From the moment we type a URL into our browser and hit Enter, a complex series of events is set into motion, involving various layers of the web stack. In this article, we’ll unravel the mystery behind what happens when we type “<a href="https://www.google.com/">https://www.google.com</a>&quot; into our browser, step by step.</p><h3>Setting Sail with a URL</h3><p>As we start our journey to our destination, we need to type in the url which we’d like to access. In this case, our journey starts from when we enter “<a href="https://www.google.com/">https://www.google.com</a>&quot; into a browser. Let&#39;s break this down to understand the whole concept a bit more.</p><p>Say the web browser is the ship we’re using to set sail. A <a href="https://www.mozilla.org/en-US/firefox/browsers/what-is-a-browser/"><strong>web browser</strong> </a>takes you anywhere on the internet, letting you see text, images and video from anywhere in the world. The <strong><em>URL (Universal Resource Locator)</em> </strong>is what tells the browser where to look and what to look for — as a map does.</p><p>Let’s break down the URL “https://www.google.com”:</p><ul><li><strong>https(Hypertext Transfer Protocol Secure)</strong>: this is called the <a href="https://blog.hubspot.com/marketing/parts-url#:~:text=A%20URL%20consists%20of%20ten,basic%20parts%20of%20a%20URL."><strong>protocol</strong></a><strong> </strong>section — it tells web servers which protocol to use when it accesses a page on a website. The https is the most common protocol and it tells your web browser to encrypt any information you enter onto the page, like your passwords or credit card information, so cybercriminals can’t access it.</li><li><a href="http://www.google.com/"><strong>www.google.com</strong></a> — the <strong>domain</strong>. this part has information about who is hosting the data which you’d like to access. in this case, google is the host. This hold the information about where to find the destination of our journey. How that happens will be explored in detail in the next section.</li></ul><h3>Navigating with DNS:</h3><p>Just like how sailors use maps and compasses to find their way, your browser needs a way to find the right place on the internet. It does this by asking a special service called DNS (Domain Name System) to translate the human-friendly website name (like “google.com”) into a numerical address (like 172.217.6.78) known as the IP(Internet Protocol), that computers understand.</p><p>Typically, computers understand numbers but the way the human brains work, it would be easier to remember “www.google.com” than it would be to remember a number like 172.217.6.78.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JUFwWI0gCwts30XAN2yMRg.png" /></figure><p>So now we know exactly where we’re going. The journey begins!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*40kJABkzFu33reJKL766YQ.jpeg" /><figcaption>Captain Jack Sparrow setting sail into the seas</figcaption></figure><h3>Sailing Across the Seas of Data with TCP/IP:</h3><p>With the destination in mind and the coordinates in hand, your browser sets off across the vast seas of the internet towards Google servers!</p><p>As your browser sets sail towards Google’s servers, it’s gotta navigate the high seas of the internet using TCP (Transmission Control Protocol). It establishes a connection with the server hosting Gogle’s website through a three-way handshake, confirming the connection’s validity and readiness to exchange data.First thing the TCP does when receiving the data is cut it into packets in small amounts so it can be easier to track and manage.</p><p>Think of TCP as the captain of the ship, ensuring that the data packets reach their destination safely and in the right order over the internet through a series of handshake maneuvers.</p><h3>Navigating Through Firewalls:</h3><p>Now that we’ve been on the journey through various network devices, singing some sea shanties as we head towards our destination, we may encounter some rough waters, in the form of firewalls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6GtcteZLwWVW0elg6kcUw.jpeg" /></figure><p>As the TCP connection is established, data packets travel through various network devices, including firewalls. Firewalls act as a barrier between our internal network and the external internet, filtering incoming and outgoing traffic based on predefined security rules. They play a crucial role in protecting against unauthorized access and malicious activity.</p><p>Your browser needs to navigate through these gates, showing its credentials to make sure it’s allowed to pass.</p><h3>Encrypting Your Ship with HTTPS/SSL:</h3><p>In today’s cyber landscape, security is paramount. Just as you’d protect your treasure with a sturdy lock, your browser uses a special protocol called HTTPS (Hypertext Transfer Protocol Secure) to encrypt your communication with websites. This ensures that no one can eavesdrop on your conversations or tamper with your treasure.</p><p>(HTTPS) uses Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocols to establish a secure connection. When our browser connects to <a href="https://www.google.com/">https://www.google.com</a>, it initiates a secure handshake, where the server presents its SSL certificate to authenticate its identity and establish encrypted communication.</p><p>Now that we know our information is secure, we can move on with our journey knowing everything is secure.</p><h3>Finding the Right Port with Load Balancers:</h3><p>When you arrive at your destination, you might find a bustling port with many ships coming and going. Load balancers are like traffic controllers, directing your browser to the right dock where it can unload its cargo of information. This ensures that no single dock gets overloaded with too much traffic</p><p>Large-scale websites like Google handle a massive influx of user requests every second. Load balancers distribute incoming traffic across multiple servers to ensure optimal performance, reliability, and scalability. When we access Google’s website, our request may be routed to one of several data centers globally through load balancers, depending on factors like server load and geographic proximity.</p><h3>Docking at the Web Server:</h3><p>Ahoy, matey! You’ve reached the shores of the website you were looking for. Once our request reaches a server in Google’s infrastructure, a web server like Apache or Nginx processes the request. The web server is like the harbor master, ready to receive your ship and unload its cargo of web pages, images, and other treasures. It fetches the requested content and sends it back to your browser through the established TCP connection for you to explore. Web servers handle various tasks, including request parsing, content generation, and protocol handling.</p><h3>Exploring the Island with Application Servers</h3><p>Some websites are more than just static pages — they’re like bustling islands full of interactive features and hidden treasures. Application servers are like the island’s guides, helping your browser navigate through the maze of dynamic content, process your requests (like search queries or form submissions), and uncover hidden gems.</p><h3>Digging for Treasure in Databases</h3><p>Beneath the surface of the island lies a vast treasure trove of data — user profiles, product listings, and more. Databases are like the island’s treasure vaults, storing and organizing this valuable information. When your browser needs to find a specific piece of information, like the price of a product or the latest news article, it digs into the database to uncover the treasure.</p><p>Databases store and manage vast amounts of structured data, ranging from user information to indexed web pages. When we interact with dynamic websites like Google, application servers may query databases to retrieve or update information based on our requests. Databases play a crucial role in storing and retrieving data efficiently, ensuring the responsiveness and reliability of web applications.</p><h3>Conclusion:</h3><p>And there you have it — a grand digital odyssey through the wonders of the internet, from setting sail with a URL to uncovering hidden treasures in databases. As we reach the end of our journey, we gain a newfound appreciation for the intricate web of technologies working seamlessly together. From DNS resolution to SSL encryption, load balancing to database queries, each component plays a vital role in delivering the web content we interact with daily.</p><p>Just like any great adventure, the journey through the internet is filled with excitement, discovery, and the promise of new horizons to explore.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0346469cb453" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>