<?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 Moses Gichia on Medium]]></title>
        <description><![CDATA[Stories by Moses Gichia on Medium]]></description>
        <link>https://medium.com/@morsewallace254?source=rss-2c77689d3b5e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Moses Gichia on Medium</title>
            <link>https://medium.com/@morsewallace254?source=rss-2c77689d3b5e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:37:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@morsewallace254/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[Burudika Ventures]]></title>
            <link>https://medium.com/@morsewallace254/burudika-ventures-774c849b1e65?source=rss-2c77689d3b5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/774c849b1e65</guid>
            <category><![CDATA[hotel-booking]]></category>
            <category><![CDATA[web-app-security]]></category>
            <category><![CDATA[car-hire]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[burudika-ventures]]></category>
            <dc:creator><![CDATA[Moses Gichia]]></dc:creator>
            <pubDate>Thu, 14 Dec 2023 01:05:09 GMT</pubDate>
            <atom:updated>2023-12-14T01:05:09.761Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Purpose: </strong><a href="https://burudika.netlify.app/hotel/">Burudika Ventures</a> is a web application designed to streamline the process for service providers to post their offerings while enabling customers to conveniently hire vehicles and book hotels in one unified platform. The goal is to create a seamless and efficient experience for both service providers and customers.</p><p><strong>Team Members:</strong></p><ul><li><strong>Moses Gichia :</strong> Project Manager / UX/UI Designer</li><li><strong>Edward Kaboi:</strong> Backend Developer</li><li><strong>Evalyn Wanjiku:</strong> Sales Executive</li></ul><p><strong>Roles and Timeline:</strong> Edward Kaboi led the development efforts, ensuring the functionality of the platform. Moses Gichia focused on creating an intuitive user interface and experience. As the project manager, my role involved coordinating the team, managing timelines, and ensuring the overall success of the project. The timeline for the project spanned 12th April 2022 to 2nd January 2024, with milestones set for key deliverables.</p><p><strong>Target Audience:</strong> Burudika Ventures caters to both service providers and customers. Service providers, including vehicle rental agencies and hotels, can efficiently showcase their services, while customers can easily browse and book the services they need.</p><p><strong>Personal Focus:</strong> As the project manager, my primary focus was on coordinating the efforts of the development and design teams. This included ensuring effective communication, setting and tracking milestones, and overseeing the overall progress of the project. My goal was to create a platform that met the needs of both service providers and customers while maintaining a user-friendly experience.</p><p><strong>Story time:</strong></p><blockquote>Embarking on the journey of Burudika Ventures wasn’t just a project for me; it was a personal odyssey that intertwined professional reinvention and a commitment to building something meaningful.</blockquote><blockquote>Nine months ago, I stood at a crossroads, having spent five years as a dedicated mechanic monitoring hydraulic systems at a button factory. The factory’s closure left 350 workers, including me, facing an uncertain future. With a wife and two daughters relying on my decisions, I made a daring choice to transition from the familiar world of machinery to the uncharted territories of software engineering.</blockquote><blockquote>The move brought me to a new city and a transformative experience at Holberton School. It was during this time that I found myself working with a passionate team at Burudika Ventures. While I wasn’t initially drawn to the world of service providers, vehicle rentals, and hotel bookings, the project presented an intriguing technical challenge that resonated with my newfound coding skills.</blockquote><blockquote>My personal connection to the project materialized through an unexpected avenue — helping a close engineering friend who faced a daily struggle. Over lunches and brainstorming sessions, he shared the challenge of finding the optimal bike route with the least uphill on his commute. This revelation sparked a realization for me: the project wasn’t just about lines of code; it was about solving a real problem and making a tangible impact on someone’s daily life.</blockquote><blockquote>As the project manager, my role evolved beyond coordinating tasks and timelines. It became a mission to create a platform that simplifies the lives of both service providers and customers, drawing on my own experiences of navigating life’s uncertainties. The project was no longer just a technical challenge; it became a testament to resilience and adaptability.</blockquote><blockquote>Fast forward to the completion of our project, and I found myself not just celebrating the successful launch of Burudika Ventures but reflecting on the transformative journey it symbolized. The project wasn’t just about creating a web application; it was about embracing change, finding purpose in challenges, and creating opportunities where none seemed to exist. Burudika Ventures became a chapter in my personal story, illustrating that sometimes, the most unexpected paths lead to the most fulfilling destinations.</blockquote><p>Burudika Ventures has successfully evolved into a robust web application, providing a seamless platform for service providers to showcase their offerings while enabling customers to effortlessly hire vehicles and book hotels. The project’s architecture, depicted in the diagram below, illustrates the smooth flow of data through the application.</p><p><strong>Architecture Diagram:</strong></p><p>[Insert Architecture Diagram Here]</p><p><strong>Technologies and Choices:</strong> For the frontend, we strategically employed HTML, CSS, Bootstrap, and Tailwind. The choice to combine Bootstrap for structure and Tailwind for more fine-grained styling allowed us to balance rapid development with the flexibility to create a unique and visually appealing user interface.</p><p>On the backend, AdonisJS and TypeScript formed the core technologies. AdonisJS, with its MVC architecture and robust features, provided a solid foundation for building scalable and maintainable server-side logic. TypeScript enhanced the development process by introducing static typing, catching errors early in the development cycle, and improving code maintainability.</p><p>MySQL served as the database management system, offering a reliable and efficient solution for storing and retrieving data. Our decision to use MySQL was driven by its proven performance, data integrity features, and compatibility with the overall tech stack.</p><p><strong>Key Features:</strong></p><ol><li><strong>User Authentication and Authorization:</strong></li></ol><ul><li>Feature: Implemented OAuth authentication via Facebook, enhancing the security and convenience of user access.</li><li>Context: This feature adds tangible value to users by providing a secure and user-friendly authentication method, leveraging Facebook’s OAuth capabilities.</li></ul><p><strong>2. Responsive Design for Mobile Compatibility:</strong></p><ul><li>Feature: Ensured the website is responsive and compatible with mobile devices.</li><li>Context: This feature significantly improves the user experience, allowing customers and service providers to access Burudika Ventures seamlessly from their mobile devices.</li></ul><p><strong>3. Custom API Integration:</strong></p><ul><li>Feature: Developed a custom API to facilitate smooth communication between the frontend and backend.</li><li>Context: The custom API ensures efficient data exchange, enabling real-time updates and interactions within the Burudika Ventures ecosystem.</li></ul><p>These features collectively contribute to the success of Burudika Ventures, delivering a user-centric platform that meets the needs of both service providers and customers.</p><p><strong>Challenging Technical Situation: Securing Facebook OAuth for User Authentication</strong></p><p><strong>Situation:</strong> In the early stages of the Burudika Ventures project, I aimed to implement Facebook OAuth for user authentication, envisioning a seamless and secure login experience. The decision to integrate Facebook’s authentication system was driven by its potential to expand our user base. However, this choice brought forth a significant challenge — the need for secure deployment through SSL.</p><p><strong>Task:</strong> With a mere 30 hours left before the project deadline, I faced the task of deploying the application securely and obtaining an SSL certificate to enable Facebook OAuth. This involved delving into SSL setup, deployment intricacies, and understanding the intricacies of Facebook’s OAuth implementation.</p><p><strong>Action:</strong> To tackle the challenge, I initiated a collaborative effort, reaching out to five peers and the technical staff for support. Following a comprehensive tutorial, I encountered a roadblock where the authentication request was successfully sent, but the login token seemed elusive. Creating a detailed diagram to illustrate the issue, I sought assistance on Facebook’s developer forums.</p><p>An unexpected breakthrough came when a Facebook engineer agreed to meet in person in exchange for a cup of coffee. Presenting my diagram, she identified a missing parameter in the authentication request and clarified the significance of another parameter indicating a response requirement. With a mere five hours remaining before the project presentation, I swiftly adjusted the parameters, finally achieving a functional Facebook OAuth integration.</p><p><strong>Result:</strong> The successful resolution of this complex technical challenge ensured the implementation of Facebook OAuth for secure user authentication within the project’s tight deadline. This experience not only strengthened my understanding of SSL deployment and OAuth intricacies but also highlighted the power of collaboration and resourcefulness in overcoming formidable technical hurdles.</p><p><em>Note: While the Facebook OAuth challenge was resolved, it’s essential to acknowledge that authentication and payment components are still in development.</em></p><p><strong>Technical Takeaways:</strong> This project has been a profound learning experience, enriching my technical skills and deepening my understanding of the intricacies of web application development. Working extensively with HTML, CSS, Bootstrap, Tailwind, AdonisJS, TypeScript, and MySQL has broadened my toolkit. The challenge of implementing Facebook OAuth highlighted the critical importance of secure deployment and thorough parameter handling in authentication systems. This experience reinforced the value of comprehensive testing and collaboration when integrating third-party services.</p><p><strong>Reflections on What I Might Do Differently:</strong> Looking back, I recognize the importance of early and meticulous planning, especially when dealing with intricate features like authentication. In future projects, I would allocate more time for potential roadblocks, ensuring a smoother development process. Additionally, maintaining a more continuous integration and deployment pipeline could streamline the debugging and testing phases, preventing last-minute challenges.</p><p><strong>Insights into Myself as an Engineer:</strong> This project unveiled my resilience and adaptability in the face of technical challenges. The successful resolution of the Facebook OAuth implementation showcased my ability to leverage collaboration and seek help when needed. I’ve also discovered a passion for problem-solving and the satisfaction derived from overcoming complex technical hurdles.</p><p><strong>Impact on My Engineering Path:</strong> Burudika Ventures has significantly shaped my engineering path. The exposure to a diverse set of technologies, combined with the hands-on experience of addressing real-world challenges, has strengthened my confidence as a software engineer. The project’s emphasis on user-centric features and seamless integration has instilled in me a commitment to delivering not just functional but also user-friendly applications. As I move forward, I plan to delve deeper into areas such as security protocols, user experience design, and continuous integration to enhance my skill set.</p><p><strong>Confirmation and Questioning of Beliefs:</strong> This project both confirmed and challenged my belief in the power of collaboration. The success of resolving the Facebook OAuth challenge through collaboration reinforced the significance of teamwork in overcoming complex issues. However, it also prompted a reflection on the need for more proactive planning and potential adjustments to my approach in future collaborations.</p><p>In conclusion, Burudika Ventures has been a transformative journey, offering not only technical knowledge but also valuable insights into my own capabilities and areas for future growth. As I navigate my engineering path, I carry forward the lessons learned from this project, eager to apply them to new challenges and opportunities.</p><p><strong>About Me:</strong> I am a passionate and adaptable software engineer | Security analyst, driven by a curiosity for solving complex problems and a commitment to delivering user-centric applications. With a background in cyber security, my journey into the world of software development has been transformative. Burudika Ventures is a testament to my dedication to learning and applying new technologies. Beyond coding, I thrive on collaboration, problem-solving, and the continuous pursuit of knowledge to elevate my engineering skills.</p><p><strong>Project Links:</strong></p><ul><li><strong>GitHub Repository:</strong> <a href="https://github.com/fr13nd-x/proj">Burudika Ventures GitHub</a></li><li><strong>Deployed Project:</strong> <a href="https://burudika.netlify.app/hotel/">Burudika Ventures</a></li><li><strong>Project Landing Page:</strong> <a href="https://burudika.netlify.app/hotel/">Burudika Ventures Landing Page</a></li><li><strong>LinkedIn Profile: </strong><a href="https://www.linkedin.com/in/mosesgichia/">My LinkedIn Profile</a></li></ul><p>Feel free to click on the links to explore the project and learn more about my journey in software engineering!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=774c849b1e65" 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/@morsewallace254/what-happens-when-you-type-google-com-in-your-browser-and-press-enter-90fb10a76c5f?source=rss-2c77689d3b5e------2</link>
            <guid isPermaLink="false">https://medium.com/p/90fb10a76c5f</guid>
            <dc:creator><![CDATA[Moses Gichia]]></dc:creator>
            <pubDate>Sun, 15 Oct 2023 22:51:15 GMT</pubDate>
            <atom:updated>2023-10-15T22:51:15.511Z</atom:updated>
            <content:encoded><![CDATA[<p>Certainly, a common curiosity many of us share revolves around the question, “What transpires when we input a URL into our web browser and press ‘Enter’?” It can be quite beneficial to possess a basic understanding of the intricacies involved in the transfer of data from the internet to our personal computers and the operations that transpire within our web browsers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YwzvQvFBdPG9zyTE9ktouw.png" /></figure><p>In this piece, I’ll attempt to answer many of your questions about the inner workings of your browser and the transmission of data to our computers through the Internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*I3WudXjRbno0jg5F.jpeg" /></figure><p><strong>DNS REQUEST</strong></p><p>When a user enters a URL and clicks Enter, the browser must first determine the IP address of the server that is hosting the webpage. This is achieved by using a DNS query, also known as a DNS request, in which the user’s computer (a DNS client) requests a DNS server’s response with the IP address for the domain name (a computer server that contains a database of public IP addresses and their associated hostnames.)</p><p>When an IP address is still unknown, it first checks the browser and/or OS cache before moving on to the Resolver server, which is often your Internet service provider. All resolvers are required to know where to find the root servers, which in turn know where to find the <strong>.COM</strong> <em>TLD </em>(Top-Level Domain) server. In the event that the resolver is unable to discover <a href="https://www.google.com/">https://www.google.com</a>, the root server informs it of where to find the <strong>.COM</strong> <em>TLD </em>server. In order to avoid having to query the root server again and making another journey, the resolver first caches this information. When contacted by the <strong>.COM</strong> <em>TLD</em> server, the server, if it is unaware of the IP address, offers the authoritative name servers for google.com. Once more, the resolver saves this fresh data. The final authority in charge of processing requests of this kind is the authoritative name server. After obtaining the IP address and saving it, the resolver returns home to provide the OS with this data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*f3FNciUaL2mjhBF3.png" /></figure><p>DNS Request</p><p><strong>TCP/IP</strong></p><p>The browser sends a request to the website’s server to start a conversation with it. However, no communication can be accomplished without having a shared language or message format, hence TCP/IP is employed as a connecting technique.</p><p>TCP/IP is a set of guidelines for internet-connected computer systems that are conceived in layers. The layers are listed below:</p><ol><li>The first layer, <strong>the Application layer</strong>, is where applications like your browser communicate directly. This layer includes protocols such as HTTP (for viewing websites) and SMTP (for checking email). The Application layer receives data from the browser and sends it to the second layer through a port.</li><li>TCP and a second scheme called UDP are both present in the Transport Layer, which is the second layer. In order for TCP to understand where the data is coming from, each application layer protocol utilizes a separate port to interact with this layer. Once the data has been received by TCP, it divides it into smaller units known as segments, commonly referred to as packets, so that each one may travel the shortest distance possible. TCP appends a header to each segment that contains instructions on what order to reassemble the segments into as well as error checking information so that the computer can determine whether the segments arrived without any problems in order to reunite them properly when they reach their destination. The segments are then put onto the third layer after this is complete.</li><li>The third layer, the <strong>Internet Layer</strong>, receives the segments and appends the origin and destination IP addresses to each segment so that regardless of the path the segments may travel, they are aware of their origin and destination. After that, the segments are sent to the top layer.</li><li><strong>The Network Access Layer.</strong> Data transmission between two devices connected to the same network is handled by it. It specifies how the data should be physically sent across the network.</li></ol><p>Typical TCP/IP protocols comprise;</p><p>1. A web server and a web browser communicate via the Hypertext Transfer Protocol (HTTP).<br>2. HTTP Secure manages secure communication between a web server and a web browser (an http with an’s’ — https, like in our URL).<br>3. File Transfer Protocol controls computer-to-computer file transfer.</p><p>At this point, your computer essentially just says, “Hey, I need the content of <a href="https://www.google.com/">https://www.google.com</a>,&quot; using the “https” language, and the server on the IP answers with the web pages based on the agreed-upon language.</p><p><strong>FIREWALLS</strong></p><p>Network security tools called firewalls keep an eye on both incoming and outgoing network traffic before deciding whether to allow or restrict a particular type of communication in accordance with predefined criteria. The conversation and any relevant packets exchanged with <a href="https://www.google.com/">https://www.google.com</a> are tracked until the connection is stopped with a firewall configured on your machine. As a result, the danger of malware assaults is significantly decreased, which is particularly beneficial for enabling safe communication over the internet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*UUj25U4kqddUB2aV.png" /></figure><p><strong>HTTPS/SSL</strong></p><p>Earlier, it was said that https handles encrypted communication between a web server and a web browser. Typically, SSL is responsible for the security provided by https (Secure Sockets Layer). A communication technology called SSL makes it easier to establish trusted connections and send encrypted data and packets between networked devices.</p><p>So, before any more data is transferred, an SSL handshake process is performed at the beginning of connection between your computer and <a href="https://www.google.com/">https://www.google.com</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*dykJ9fs5mAnREciR.png" /></figure><p><strong>LOAD-BALANCER</strong></p><p>Google searches are something we all do every single day. If there is only one server for <a href="https://www.google.com/">https://www.google.com</a>, your browser may experience delays in displaying the site’s content, assuming it even reaches the site at all. This is because there are often millions of people all trying to access the same page at the same time. Companies like Google provide multiple high-capacity servers, each with a unique IP address, to handle the traffic to <a href="https://www.google.com/">https://www.google.com</a>. Even when there are several servers available, traffic from various parts of the world still needs to be balanced across them. This is where a load balancer comes in.</p><p>Load-balancers, in this context, are programs or pieces of hardware that route requests for servers from clients to many servers in the same network. Load balancing is the practice of using multiple scheduling algorithms in concert inside a single piece of software. Load balancers, on the hardware side, are sometimes referred to as specialized routers or switches and are placed between the servers and the clients.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*cdNN-cn0UDzE3AZd.jpeg" /></figure><p><strong>WEB SERVER &amp; APPLICATION SERVER</strong></p><p>A web server is a computer system that processes requests from users on the World Wide Web and sends back data using the Hypertext Transfer Protocol (HTTP) and other protocols. Its primary responsibility is to show website content by storing, processing, and delivering web pages to visitors.</p><p>In contrast to a web server, which was designed to primarily serve static material, an application server is capable of serving dynamic content, performing business logic for enterprise applications, and incorporating a number of different protocols for client response.</p><p>For example, when you type in “<a href="https://www.google.com/">https://www.google.com</a>&quot; in your browser, the server will respond and send the requested page to your computer.</p><p><strong>DATABASE</strong></p><p>Databases store data in a structured style that facilitates quick searches and regular maintenance. Any kind of information can be saved, managed, and retrieved with the help of a database. This information has been gathered in a systematic fashion.</p><p>The Database Management system makes it possible to manage data by storing information about users, updating information about location and time zone, managing session data, and so on. It enables the maintenance of well-organized data within a structure that is both aesthetically pleasing and functionally sound. In order to retrieve data from the database system, store data, modify data, or remove data, the application server communicates with the database server via the database system. In line with the request, given that we are in the process of accessing the Google homepage, the database will be queried for location information taking our IP address into consideration. As a result, an HTML page that is more tailored to our needs will be prepared by the application server and delivered to us.</p><p>In conclusion, these are just a few fundamental insights into how the internet functions. I trust that this has provided some value to those inquisitive about the process of typing a URL like “<a href="https://www.google.com/">https://www.google.com</a>&quot; into a browser and hitting the enter key. I extend my heartfelt thanks for your visit and look forward to welcoming you back in the near future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90fb10a76c5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>