<?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 David Okolie on Medium]]></title>
        <description><![CDATA[Stories by David Okolie on Medium]]></description>
        <link>https://medium.com/@David-Okolie?source=rss-6eb69a1f42ca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fekPXR00VWlkc1l1fLo_ww.jpeg</url>
            <title>Stories by David Okolie on Medium</title>
            <link>https://medium.com/@David-Okolie?source=rss-6eb69a1f42ca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:02:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@David-Okolie/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[Building Ajuju: A Journey of Lessons in Backend (RESTful API) Development]]></title>
            <link>https://medium.com/@David-Okolie/building-ajuju-a-journey-of-lessons-in-backend-restful-api-development-e296a1e6a725?source=rss-6eb69a1f42ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/e296a1e6a725</guid>
            <dc:creator><![CDATA[David Okolie]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 10:31:06 GMT</pubDate>
            <atom:updated>2023-07-21T10:32:12.788Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXKLa4uwOi7KSS5uVKppzA.png" /></figure><h3>Introduction</h3><p>As I graduate from the ALX Software Engineering program, I reflect on my portfolio project, Ajuju, a robust backend RESTful API service for a Q&amp;A platform. The development journey has been transformative, filled with challenges and breakthroughs that have enhanced my understanding of architecture, system design, separation of concerns, and best practices in API development. These concepts are at the heart of creating a scalable and maintainable application.</p><p>In this article, I will share some insights I gleaned during the development process. They are in no way exhaustive or altogether perfect as these concepts can be quite broad and deep, and I am still learning. But these are definitely steps in the right direction and a kind of general overview for anyone interested in backend development.</p><h3>Architecture and System Design</h3><h4><strong>Importance of Architecture and Separation of Concerns</strong></h4><p>Imagine building a house without a general layout or blueprint. Chaos would ensue, and the end result would be far from perfect. Similarly, in software development, architecture serves as the blueprint that ensures our application stands strong and well-organized.</p><p>One of the most crucial concepts I learned was the “separation of concerns.” This principle dictates that different parts of the application should focus on specific tasks, making the codebase more modular and maintainable. With this approach, each component has a clear responsibility, and changes can be made without affecting the rest of the system.</p><h4><strong>Request Flow Breakdown:</strong></h4><p>Now, let’s dive into the heart of Ajuju’s backend architecture — the request flow.</p><figure><img alt="diagram showing request flow through the application" src="https://cdn-images-1.medium.com/max/582/1*rFFoZ49naHTKnSDX902NVw.png" /><figcaption>Simplified request flow for Ajuju</figcaption></figure><h4><strong>Each component in the request flow plays a vital role:</strong></h4><p><strong>Client:</strong> Initiates requests to the API Endpoints, enabling user interaction with the application. I mostly used <a href="https://learning.postman.com/docs/getting-started/overview/"><strong>Postman</strong></a> to mimic a client consuming the API</p><p><strong>API Endpoints:</strong> Receives incoming requests and directs them to the appropriate Auth Middleware or Request Handler.</p><p><strong>Auth Middleware:</strong> Handles user authentication before passing the request to the Request Handler.</p><p><strong>Request Handler:</strong> Interacts with the Controllers to perform the necessary business logic based on the request.</p><p><strong>Controllers:</strong> Contain the application’s logic and interact with the Data Access Layer to retrieve or modify data.</p><p><strong>Data Access Layer (DAL)</strong>: Acts as a bridge between Controllers and the Database, abstracting data retrieval and manipulation.</p><p><strong>Database:</strong> The foundation of the system, storing and managing data.</p><h4><strong>By separating concerns, we achieve several advantages:</strong></h4><p>This separation of concerns allows for modularity and scalability. The data access layer acts as a buffer, enabling easy swapping of databases, while the routing framework can be replaced without affecting the core functionalities handled by the controllers.</p><p><strong>Database Swappability:</strong> Since the Controllers interact with the DAL, we can easily swap out the underlying database without affecting the rest of the application. This flexibility is invaluable when choosing between various databases or for testing purposes.</p><p><strong>Flexibility in Request Framework:</strong> By abstracting request handling into the Request Handler, we can easily replace the routing framework (such as ExpressJS) without rewriting the entire codebase. This gives us the freedom to experiment with different frameworks or adopt new ones in the future.</p><h3><strong>Junction Tables</strong></h3><p>In the world of web applications, establishing connections between users is a common and essential requirement. Take a social media platform, for instance. Users can follow and be followed by others, creating a network of relationships. However, managing these complex many-to-many relationships efficiently can be a daunting task. This is where junction tables come to the rescue!</p><p>In Ajuju, junction tables were utilized to model the relationships between users and their followers/followings. This approach allows for efficient and scalable representation of many-to-many relationships, creating a seamless connection within the application.</p><h4>Understanding Junction Tables: Untangling Complex Relationships</h4><p><strong>Junction tables</strong>, also known as associative or link tables, act as mediators between entities that have a <strong>many-to-many relationship</strong>. In simple terms, they allow us to connect multiple records from one table to multiple records in another table. This elegant solution resolves the complexity of managing such relationships directly in the primary tables.</p><p>Let’s visualize the concept with a simple example of how it’s used in Ajuju, users can follow and be followed by other users. We want to create a seamless way to represent these relationships and quickly query and update them.</p><h4>Setting the Stage: Database Schema</h4><p>To achieve our goal, we first need to design our database schema. In Ajuju, we have a users table and a follows table. The users table stores user information, such as username, email, and hashed passwords. The follows table is where the magic happens. It consists of two foreign keys referencing the users table, representing the follower and the ‘followee’, respectively.</p><pre>  +------------------+           +-----------------------+<br>  |     Users        |           |       Follows         |<br>  +------------------+           +-----------------------+<br>  |  id (PK)         |           |  follower_id (FK)     |<br>  |  username        |   +---&gt;   |  following_id (FK)    |<br>  |  email           |           +-----------------------+<br>  |  hashed_password |<br>  +------------------+</pre><p>With our database schema in place, let’s delve into how we utilize junction tables to implement the follower/following feature in Ajuju.</p><h4>The Junction Table — “Follows”:</h4><p>The “Follows” junction table plays a pivotal role in managing the complex follower/following relationships between users. Let’s take a closer look at its structure and significance:</p><pre>model Follows {<br>  followerId  Int<br>  followingId Int<br>  follower    User @relation(&quot;follower&quot;, fields: [followerId], references: [id])<br>  following   User @relation(&quot;following&quot;, fields: [followingId], references: [id])<br>  @@id([followerId, followingId])<br>}</pre><ol><li><strong>Structure:</strong></li></ol><p>The “Follows” table contains two foreign key columns: “followerId” and “followingId,” referencing the “id” column of the User table. By utilizing these foreign keys, we establish a link between users who follow others (“follower”) and users who are being followed (“following”).</p><p><strong>2. Significance:</strong></p><p>Junction tables ensure that each relationship between users is represented as a distinct entry. By introducing this intermediary table, we prevent redundant data storage and improve data integrity.</p><h4>Implementing the Follower/Following Feature:</h4><p>Let’s explore how the “Follows” junction table facilitates the seamless implementation of the follower/following feature in Ajuju:</p><p><strong>Follow a User:</strong></p><ul><li>When a user decides to follow another user, Ajuju inserts a new entry in the “Follows” table.</li><li>The new entry records the “followerId” (the user who follows) and the “followingId” (the user being followed).</li></ul><p><strong>Fetch Followers and Following:</strong></p><ul><li>To retrieve a user’s followers, Ajuju queries the “Follows” table based on the “followingId.”</li><li>Similarly, to get users followed by a specific user, Ajuju queries the “Follows” table based on the “followerId.”</li></ul><h4>Benefits and Scalability of Junctions Tables:</h4><p>The use of junction tables in Ajuju can yield several advantages and ensures the scalability of the application:</p><p><strong>Data Integrity:</strong> Junction tables maintain data consistency, eliminating duplicate relationships between users. This approach enhances the reliability and efficiency of data retrieval.</p><p><strong>Flexibility:</strong> Say Ajuju expands, junction tables offer a flexible way to manage complex many-to-many relationships without altering existing data structures.</p><p><strong>Easier Updates:</strong> Modifying or updating follower/following relationships becomes straightforward with junction tables, ensuring smooth user interactions.</p><h3>Voting with Enum Types — A Notation</h3><p>Let’s visualize how voting takes place in Ajuju with Enum types:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*-WrK8l3KP-MfSvpvSSx1KQ.png" /></figure><p>When a user casts their vote, the corresponding Enum value (UPVOTE or DOWNVOTE) is recorded in the voteType field of either QuestionVote or AnswerVote, depending on their action.</p><p>The implementation of a robust voting system plays a pivotal role in allowing users to express their opinions on questions and answers. One of the essential components enabling this functionality is the use of Enum types, a powerful feature in the <a href="https://www.prisma.io/docs"><strong>Prisma ORM</strong></a>.</p><h4>What are Enum Types?</h4><p>Enum types represent fixed sets of constants. They offer a concise and structured way to define a specific domain of values, ensuring data consistency and clarity throughout the codebase. In Ajuju, Enum types are employed to handle the two distinct voting actions: UPVOTE and DOWNVOTE.</p><p>To illustrate the power of Enum types, let’s take a look at how they are defined in Ajuju’s data model:</p><pre>model QuestionVote {<br>  id         Int      @id @default(autoincrement())<br>  voteType   VoteType<br>  createdAt  DateTime @default(now())<br>  userId     Int<br>  questionId Int<br>  user       User     @relation(fields: [userId], references: [id])<br>  question   Question @relation(fields: [questionId], references: [id], onDelete: Cascade)<br>}<br><br>model AnswerVote {<br>  id        Int      @id @default(autoincrement())<br>  voteType  VoteType<br>  createdAt DateTime @default(now())<br>  userId    Int<br>  answerId  Int<br>  user      User     @relation(fields: [userId], references: [id])<br>  answer    Answer   @relation(fields: [answerId], references: [id], onDelete: Cascade)<br>}<br><br>enum VoteType {<br>  UPVOTE<br>  DOWNVOTE<br>}</pre><p>In the data model above, two entities are introduced: QuestionVote and AnswerVote. Each entity contains a voteType field, which accepts values from the VoteType Enum. This ensures that voting actions are restricted to only UPVOTE or DOWNVOTE, maintaining a consistent and unambiguous voting system.</p><p>When a user casts their vote on a question or an answer, the appropriate voteType value is stored in the database, indicating the nature of the vote.</p><h4>Advantages of Enum Types</h4><p><strong>Data Consistency:</strong> Enum types restrict the valid values for voting actions, ensuring only the allowed values are used. This enforces data consistency and prevents invalid votes from being recorded.</p><p><strong>Code Clarity:</strong> Enum types enhance code readability by providing meaningful names for voting actions. Developers can easily understand the purpose of a vote when reviewing the codebase.</p><h3>Asynchronous Communication Through RabbitMQ</h3><p>At the heart of Ajuju’s architecture lies <a href="https://www.rabbitmq.com/">RabbitMQ</a>, a versatile message broker. Let’s explore how RabbitMQ’s capabilities were harnessed to enable seamless asynchronous communication and optimize the system’s performance.</p><h4><em>Overview of RabbitMQ</em></h4><p>RabbitMQ, depicted below, acts as the intermediary between our app’s components, ensuring smooth communication and coordination.</p><pre>                +--------------+<br>                |              |<br>                |   RabbitMQ   |<br>                |              |<br>                +--------------+<br>                     |     |<br>   +-----------------+     +-------------------+<br>   |                                           |<br>   |               Ajuju Application           |<br>   |                                           |<br>   +-------------------------------------------+</pre><p><strong><em>Asynchronous Communication for a Smoother Experience</em></strong></p><p>Ajuju’s architecture embraces the asynchronous paradigm, empowering it to decouple time-consuming tasks from the main application flow. RabbitMQ’s message queues play a vital role in enabling asynchronous interactions, as illustrated here:</p><pre>                      +--------------+<br>     Request Flow     |              |       Background Processing<br>   +---------------&gt;  |   RabbitMQ   |  +----------------------&gt;<br>                      |              |     (e.g Send Email, etc.)<br>                      +--------------+</pre><p>By employing RabbitMQ, the core application was freed from non-essential tasks like sending emails, so users enjoy a seamless experience, even during resource-intensive operations.</p><p>RabbitMQ was harnessed to send emails in Ajuju. A producer-consumer pattern was put in place, ensuring that emails are sent asynchronously, reducing response times and enhancing user satisfaction. It enabled efficient message queuing and communication between different components. Its implementation improved the responsiveness and overall performance of the API.</p><h3>Code Review and Refactoring</h3><pre>   ┌────────────────┐        ┌─────────────────┐        ┌─────────────────┐<br>   │  Initial Code  │ -----&gt; │   Code Review   │ -----&gt; │    Refactored   │<br>   │  Organization  │        │   and Feedback  │        │    Codebase     │<br>   └────────────────┘        └─────────────────┘        └─────────────────┘<br><br>╭──────────────────────────────────────────────────────────────────────────╮<br>│                                                                          │<br>│ The initial codebase of Ajuju was a functional MVP, but it lacked proper │<br>│ organization and separation of concerns. E.g. Controllers handled        │<br>│ requests and transacted with the database directly, making it hard to    │<br>│ ensure future scalability and challenging to mock aspects for unit tests.│<br>│                                                                          │<br>╰──────────────────────────────────────────────────────────────────────────╯</pre><p>In the early stages of developing Ajuju, the code organization was simplistic, but as the project grew, it became evident that the lack of proper separation of concerns led to tangled and unmaintainable code. Code reviews played a vital role in identifying these challenges.</p><p><strong>Code Review and its Importance</strong></p><p>Code reviews in my case allowed very experienced sets of eyes to scrutinize the codebase, uncovering potential issues and providing valuable feedback. It was a process that fostered access to practical insights and helped catch bugs and security vulnerabilities early.</p><p><strong>Challenges and the Path to Refactoring</strong></p><p>One significant challenge was the lack of separation between request handling and controllers. This made it difficult to isolate functionalities for testing, leading to limited unit tests and potential bugs. To address this, a refactoring process was undertaken to create a clear separation between these concerns.</p><p><strong>Improving Maintainability through Refactoring</strong></p><p>Refactoring involved dividing the codebase into smaller modules, each responsible for specific tasks. Controllers were now solely responsible for handling business logic, while routes focused on request handling and validation.</p><pre>// sample Old Code - Controller handling request, business logic and database queries together<br>class AnswerController {<br>  static async createAnswer(req: Request, res: Response) {<br>    ...<br>    const question = prisma.question.findUnique({<br>      ...<br>    });<br>    const answer = prisma.answer.create({<br>      ...<br>    });<br>  };<br>};<br><br>// sample Refactored Code - Separation of concerns<br># Database Access<br>const answerQuestion = (authorId: number, questionId: number, content: string) =&gt; {<br>  return prisma.answer.create({<br>    ...<br>  });<br>};<br><br>const findQuestion = (id: number) =&gt; {<br>  return prisma.question.findUnique({<br>    ...<br>  });<br>};<br><br># business Logic<br>class AnswerController {<br>  static async createAnswer({ authorId, questionId, content }: { authorId: number; questionId: number; content: string }) {<br>    ...<br>    const question = await findQuestion(questionId);<br>    ...<br>    const answer = await answerQuestion(authorId, questionId, content);<br>    ...<br>  };<br>};<br><br># request handler<br>const createAnswerHandler: RequestHandler = async (req, res) =&gt; {<br>  ...<br>  const response = await AnswerController.createAnswer({ authorId, questionId, content });<br>  ...<br>};</pre><p><strong>Mocking and Testing Advantages</strong></p><p>With the improved separation of concerns, mocking dependencies became straightforward. This enabled robust unit testing with <a href="https://www.npmjs.com/package/jest"><strong>Jest</strong></a>, ensuring the correctness of individual components in isolation. Tests became more reliable, and the codebase became more resilient to future changes.</p><p><strong>Insights and Lessons Learned</strong></p><p>The refactoring process led to valuable insights and lessons. It taught me the importance of scalable and modular code architecture. It also highlighted the significance of code readability and consistency for collaboration and maintainability.</p><h3>Error Handling</h3><p>Errors, often seen as the nemesis of developers, can be harnessed to improve user experience. By addressing errors head-on, we can turn them into opportunities for engagement and provide meaningful feedback to our users.</p><p><strong>Crafting Custom Error Messages</strong></p><p>Ajuju goes beyond generic error messages to tailor responses that speak the user’s language. By crafting custom error messages, a layer of security is added to thwart potential attacks while ensuring users are guided with clear, concise, and friendly information.</p><pre>// Instead of returning a generic error message like this:<br>return {<br>  success: false,<br>  error: &quot;Something went wrong&quot;,<br>};<br><br>// A custom error message is returned:<br>return {<br>  success: false,<br>  error: &quot;Invalid email address. Please check your input and try again.&quot;,<br>};</pre><p><strong>Prioritizing User Data Protection</strong></p><p>The trust of users is paramount so handling errors with caution, being aware of bad actors who could try to game the system, and avoiding divulging sensitive information that could compromise their data or expose vulnerabilities is paramount.</p><pre>return {<br>  success: false,<br>  error: &quot;Invalid Email or Password.&quot;,<br>});</pre><p>As I continue to grow and improve, I’m learning to turn errors into opportunities for meaningful engagement with users, ensuring that the built application remains safe and elevates the user experience and security of the application.</p><h3>Organization and Modularity</h3><h4>The Beauty of Modularity</h4><p>Imagine the codebase as a well-orchestrated symphony, each instrument playing its part harmoniously. Modularity, like the sections of a musical composition, brings structure and clarity to the project. By breaking down the app’s functionality into small, reusable modules, one creates building blocks that can be rearranged, combined, and reused to compose the masterpiece of the app.</p><pre>/ajuju<br>├── controllers<br>│   ├── questionController.js<br>│   ├── userController.js<br>│   └── ...<br>├── services<br>│   ├── authService.js<br>│   ├── emailService.js<br>│   └── ...<br>├── routes<br>│   ├── questionRoutes.js<br>│   ├── userRoutes.js<br>│   └── ...<br>├── models<br>│   ├── questionModel.js<br>│   ├── userModel.js<br>│   └── ...<br>└── ...</pre><h4>The Power of Organization</h4><p>Now, envision the codebase as an intricate maze of thoughts and ideas. Without organization, this labyrinth becomes a maze of confusion. With distinct folders and clear naming conventions, one can navigate effortlessly through the code, leaving breadcrumbs for future developers to follow.</p><h3>Secure Authentication and Input Validation</h3><p><strong>Secure authentication</strong> forms the foundation of any trustworthy application. Imagine it as a fortress protecting the user’s kingdom of data. An authentication mechanism was created for Ajuju to help stand resilient against unauthorized intrusions.</p><p>The user database acted as the first line of defense, storing <strong>hashed passwords</strong> instead of plain text. Using <a href="https://github.com/kelektiv/node.bcrypt.js"><strong>bcrypt</strong></a>, each user’s password is fortified, making it practically impossible for malicious actors to gain unauthorized access.</p><pre>        ______________             ___________________<br>       |              |           |                   |<br>       |   User DB    |           |   User Request    |<br>       |______________|           |___________________|<br>            |                               |<br>            V                               V<br>      +--------------+               +--------------+<br>      |    Ajuju     |               |    Ajuju     |<br>      |     API      |               |     API      |<br>      |______________|               |______________|</pre><p><strong>Data sanitization</strong> is the shield wielded to protect against data corruption and security breaches. Robust input validation was done by leveraging <a href="https://joi.dev/api/?v=17.9.1"><strong>joi</strong></a>. This ensured that only sanitized and authorized data entered our application.</p><p>Implementing secure authentication is pivotal in any backend development. <a href="https://www.npmjs.com/package/jsonwebtoken"><strong>JSON Web Token (JWT)</strong></a> was adopted in Ajuju to enable seamless, stateless user authentication.</p><pre>// sample implementation<br><br>// Generate JWT token<br>const generateToken = (userId: string): string =&gt; {<br>  const payload = { userId };<br>  const token = jwt.sign(payload, process.env.JWT_SECRET!, { expiresIn: &#39;1h&#39; });<br>  return token;<br>};<br><br>// Authenticate user<br>const authenticateUser = async (req: Request, res: Response, next: NextFunction) =&gt; {<br>  try {<br>    const token = req.headers.authorization?.split(&#39; &#39;)[1];<br>    if (!token) {<br>      return res.status(401).json({<br>        success: false,<br>        error: &#39;Authentication failed: Token not provided&#39;,<br>      });<br>    }<br><br>    const decodedToken = jwt.verify(token, process.env.JWT_SECRET!) as JwtPayload;<br><br>    req.userId = decodedToken.userId;<br><br>    return next();<br>  } catch (err: any) {<br>    if (err.name === &#39;JsonWebTokenError&#39;) {<br>      return jwtErrorHandler(err, req, res, next);<br>    }<br>    return next(err);<br>  }<br>};</pre><h3>Consistent Naming Conventions</h3><p>Imagine traversing an intricate codebase where variables are named haphazardly, functions are cryptically labeled, and classes are ambiguously titled. A project without a consistent naming convention resembles a labyrinth, causing confusion and increasing the likelihood of bugs.</p><h4><strong>The Naming Standard</strong></h4><p>Ajuju followed a comprehensive naming standard inspired by industry best practices. Here’s a glimpse of the guidelines:</p><p><strong>Descriptive and Intuitive:</strong> Variable names should be descriptive and intuitive, conveying their purpose and content clearly</p><pre>// Example: descriptive variable names<br>const firstName: string;<br>const hashedPassword: string;</pre><p><strong>CamelCase for Functions and Variables:</strong> Functions and variables were named using the CamelCase convention, with the first letter in lowercase and subsequent words capitalized.</p><pre>// Example: CamelCase for function names<br>const hashPassword = async (password: string): Promise&lt;string&gt; =&gt; {<br>// function body<br>};</pre><p><strong>PascalCase for Classes and Interfaces:</strong> Classes and interfaces adhered to the PascalCase convention, with the first letter of each word capitalized.</p><pre>// Example: PascalCase for class names<br>class UserController {<br>  // class methods<br>}</pre><h4>Benefits of Consistency</h4><p><strong>Readability:</strong> With a clear naming convention in place, developers can quickly understand the purpose and usage of different elements in the code.</p><p><strong>Collaboration:</strong> A shared naming standard fosters effective collaboration, enabling developers to seamlessly navigate each other’s code.</p><p><strong>Scalability:</strong> As the project expands, consistent naming eases the incorporation of new features and enhancements.</p><h3>Conclusion</h3><p>Building Ajuju has been an incredible journey of personal growth in software engineering. I have acquired some valuable knowledge in system design, architecture, and the importance of separation of concerns. As I venture further in my career, I will definitely embrace continuous learning and creativity in projects, as these attributes lead to innovative and impactful solutions.</p><p>Meanwhile, I’ll keep building. I am quite excited about the journey ahead.</p><h3>About me</h3><p>I am a unique blend of creativity, bibliophilism, and the desire to learn. I have a background in Architecture and Construction, and I am excited about solving problems.</p><p>Ajuju is on <a href="https://github.com/David-Inkheart/Ajuju"><strong><em>GitHub</em></strong></a></p><p>You can check out a video demo <a href="https://www.youtube.com/watch?v=0ruzpoQjWxk"><strong>here</strong></a></p><p>Let’s connect on <a href="https://www.linkedin.com/in/david-okolie"><strong><em>LinkedIn</em></strong></a></p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e296a1e6a725" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Adventure of Building OSBH: Triumphs, Trials, and Thrills]]></title>
            <link>https://medium.com/@David-Okolie/the-adventure-of-building-osbh-triumphs-trials-and-thrills-dc8fceb173f?source=rss-6eb69a1f42ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc8fceb173f</guid>
            <dc:creator><![CDATA[David Okolie]]></dc:creator>
            <pubDate>Wed, 05 Apr 2023 14:17:41 GMT</pubDate>
            <atom:updated>2023-04-26T10:24:57.620Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5tQdlJ4MJfPDX7-yIRs0EA.jpeg" /><figcaption>The start of a community</figcaption></figure><p><strong>Open Source Book-Hub</strong> Provides free access to diverse genres of resources including hobby-related ones and aims to reduce the challenging barriers to sharing and accessing knowledge or niche readings, by empowering learning, literary leisure, and exploration <em>through</em><strong><em> community-driven</em></strong><em> open access</em></p><p>Our team, comprising three passionate Fullstack Software Engineers — Davidson Ogaraku, Philip Ukanwoke, and myself, embarked on a challenging yet exciting project. We had just <strong>3 weeks</strong> to build something, as part of our curriculum in the ALX Software Engineering Program. Our choice goal was to create a community platform that offered a comprehensive experience for individuals to explore their interests and resources in one place.</p><p>As an engineering problem, we were able to focus on developing a seamless user experience that would be both web and mobile-friendly, find a way to source large amounts of data that would be needed and integrate third-party services to encourage joining with existing popular social media accounts.</p><p>Davidson was responsible for the business logic of the project, but he was also able to handle other stacks with ease. Philip was our own QA specialist, who took complete ownership of user and unit testing. However, he was also comfortable contributing to any other stack of the project as needed.</p><p>As part of the project, I was responsible for the front-end development. However, I also had a strong understanding of the backend and was able to seamlessly integrate business logic with the user interface and experience where necessary, or dive into any other stack as needed.</p><h3><strong>Why this project, especially for me?</strong></h3><p>Let me take you on a journey of how our team came together to build Open Source Book-Hub, a platform that revolutionizes the way we access and share knowledge and resources.</p><p>It all started with our shared passion for knowledge and literature. As a self-proclaimed bookworm, I had struggled to find quality resources that catered to my particular interests. My teammates also faced similar challenges. We wanted to create a platform that not only provided free access to diverse resources but also created a community-driven approach to knowledge sharing.</p><p>As we brainstormed ideas, we realized that our platform could be more than just a download center for books. It could also offer tutorials, blogs, and forum threads where members could share their experiences, tips, and insights. I could write as much as I wanted with admin privileges!😁 (Just kidding). This would create a wholesome experience for people with varying interests and resource needs.</p><p>But we didn’t stop there. We also wanted to make sure that our platform was user-friendly and easily accessible. So we decided to make the project web and mobile responsive to ensure that users could access the platform anywhere and anytime.</p><h3><strong>Accomplishments so far</strong></h3><p>With all these ideas and concepts in place, our team worked tirelessly to bring Open Source Book-Hub to life. And we did it! We have a working, fully hosted web community. We created a platform that provides free access to a diverse range of resources and promotes community-driven open access. It was an incredible journey of 3weeks, and I am grateful to have been a part of it.</p><p><strong>ARCHITECTURE</strong></p><p>Our App was built using Django framework, so automatically, it implements a type of Client-Server Architecture: <strong>The MTV - Model, Template, and View</strong>. This type of Architecture is usually generally and popularly known as <strong>MVC architecture</strong>. This helped us achieve our aim of code readability and maintainability by separating the presentation, business, and database layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-__Kmhn8eGlqs3e5efRCLQ.png" /><figcaption>Data flow through the application</figcaption></figure><p>The Model View Controller (MVC) architecture separates the software’s business logic and display, leading to a better division of labor and improved maintenance. The three parts of the MVC are the Model, which manages data and business logic, the View, which handles layout and display, and the Controller, which routes commands to the model and view parts. Django also follows the MVC pattern but it just uses different terminology. M — Model, T — Template (i.e View), V — View (i.e Controller)</p><p><strong>REQUEST-RESPONSE LIFECYCLE</strong></p><p>HTTP/HTTPS protocol is used for request-response communication between client and server. Our Django application uses Nginx as a Web server and Gunicorn which implements the WSGI server that handles requests to the Django application. The request from the client is first received by the web server and then passed to the WSGI server.</p><p>Django application has layers for request-response handling: Request Middlewares, URL Router, Views, Context Processors, Template Renderers, and Response Middlewares.</p><p><strong>Request Middlewares</strong> handle incoming requests and can be customized.</p><p><strong>URL Router</strong> matches the URL pattern with the incoming request path and sends it to the View.</p><p><strong>Views</strong> process the business logic using the request data and send the response to Context Processors.</p><p><strong>Context Processors</strong> add additional context data to the response, which is then used by Template Renderers.</p><p><strong>Template Renderers</strong> use the context to generate the response content, which can be in various formats.</p><p><strong>Response Middlewares</strong> process the response and add/modify header/body information before sending it back to the client/browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wd5GBpV43hR_A-NT1BU5Kw.png" /><figcaption>Request-Response Lifecycle</figcaption></figure><p><strong>TECHNOLOGIES USED FOR DEVELOPMENT</strong></p><p><strong>Ubuntu 20.04 LTS: </strong>I worked locally on this operating system based on Linux kernel. I chose those because of my familiarity with it and to further solidify my knowledge of building with it.</p><p><strong>Django Framework</strong>: As mentioned earlier, we built our backend with Django, which is a Python Framework that uses <strong>Jinja</strong> as a Template Engine. This choice was to enable a quick build and deepen our understanding of another Python framework.</p><p>Davidson already had previous experience working with Django, and we all had used Flask to build before. So when this discussion on tools to use came up, He suggested Django. I and Philip agreed because it was another opportunity to learn something new and build with it. And it has been an adventure.</p><p><strong>SQLite: </strong>This is a database that comes with Django framework, and was used during development. <strong>PostgreSQL</strong> was used for the deployment.</p><p><strong>Bootstrap 5:</strong> We chose this for our front end. It is a popular front-end web development framework with responsive design features that allow web applications to adapt to various devices. This was quite important to us, as we wanted to ensure we had a responsive, mobile-first interface. It offers customizable options, pre-built components, and accessibility features built-in, ensuring a consistent look and feel across web pages, making it easier for developers to maintain and update the code.</p><p>In addition to this, we used some <strong>vanilla Javascript and CSS</strong> to customize some aspects we couldn’t cover with Bootstrap. This further helped to improve our understanding of these tools.</p><p><strong>SOME FEATURES COMPLETED</strong></p><p><strong>OAuth via Github</strong>: By using popular social media platforms to sign in, users can easily log in and access the website without having to create a new account. This saves time and effort and also adds an extra layer of security as users can use their existing accounts and do not have to remember new passwords. We plan to add more options like Twitter and Facebook later.</p><p><strong>Library with search, preview, and pagination enabled: </strong>This makes it easy for users to find and browse through various resources available on the website. With the search and pagination feature, users can quickly locate the desired content and navigate through it without having to scroll through endless pages. They can preview to quickly read a bit without downloading if they don’t want to. This enhances the overall user experience and saves time.</p><p><strong>Blog with the ability to like and comment</strong>: This allows users to read and interact with the website’s content. With the ability to like and comment, users can express their opinions, ask questions, and engage in discussions with other users. This promotes user engagement and encourages users to revisit the website.</p><p><strong>Forum with the ability to like and comment:</strong> This allows users to participate in discussions related to various topics. With the ability to like and comment, users can share their thoughts, opinions, and feedback, and interact with other users. This fosters a sense of community and encourages users to contribute to the website.</p><p><strong>The website is responsive and compatible with mobile:</strong> With the website being responsive and mobile-friendly, users can access the project on the go and from any device. This provides users with the flexibility and convenience to access the website from anywhere and anytime, enhancing the overall user experience.</p><h3>The most difficult technical challenge we faced</h3><p>We had many challenges that we overcame one at a time as we built, one such being how to provide a vast collection of resources. We solved this by allowing members of the community to share whatever resources they could. This way, there was always someone who could provide the needed resources.</p><p>But the greatest of them all so far was the <strong>Persistence of test setup data during unit testing</strong></p><p>As a team, we were working on writing unit tests for our application. However, when we attempted to run the tests, we encountered a bug and none of the tests ran successfully, even though the application itself was functioning as intended.</p><p>We realized that the issue was related to the persistence of our test setup data and that we needed to gain a better understanding of how the tests worked and how to properly set up the test data.</p><p>Our team began debugging the issue and discovered that an in-memory test database was being created at runtime and destroyed after the tests were completed. At first, we thought that this was the reason why the test data was not persisting or being accessed during runtime. To solve the issue, we did more research and found that the <a href="https://docs.djangoproject.com/en/4.1/topics/testing/overview/"><strong><em>- -keepdb</em></strong></a> flag could be used to keep the test database and make the data accessible even after runtime. We also used a custom SQL query with the<strong><em> </em></strong><a href="https://docs.djangoproject.com/en/2.2/topics/db/sql/"><strong><em>django.db.connection</em></strong></a> object to access the content of the test database.</p><pre>&quot;&quot;&quot;<br>You can then access the in-memory database in your tests by using<br>the default database connection. <br>Here is an example of how to access the database in your tests:<br>&quot;&quot;&quot;<br><br>from django.db import connection<br><br>def test_my_model():<br>    cursor = connection.cursor()<br>    cursor.execute(&quot;SELECT * FROM myapp_mymodel&quot;)<br>    rows = cursor.fetchall()<br>    # Do something with the rows</pre><p>We later discovered that our test database was empty, and after further research, we realized that we were setting up our data incorrectly in the wrong scope. To address this issue, we ensured that the logic being used to set up, create, or fetch the data was in the same scope, which ensured that the test database was being written to and data is retrieved from the correct location.</p><p>By using the <strong><em>- -keepdb </em></strong>flag and a custom SQL query with the <strong><em>django.db.connection</em></strong> object, we were able to access the test database at or after runtime and confirm that our test data was eventually persisting. By ensuring that the data persisted and the logic being used to create or fetch the data was in the same scope, we resolved the issue related to the persistence of test setup data. These steps resulted in a more efficient testing process.</p><h3>What I have learned so far</h3><p><strong>Technically,</strong> I have been exposed to a whole lot of perspectives and tools that made building <strong>OSBH </strong>an experience. Especially building with a team.</p><p>We started with research and brainstorming ideas. We documented processes, findings, concepts, and technologies on <strong>google docs</strong> for ease of collaboration.</p><p>I learned to use <a href="https://balsamiq.com/"><strong><em>Balsamiq</em> </strong></a>for wireframing and prototyping the mockup for our MVP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LAF7DKmNeJ5lDCG4wcPgOQ.png" /><figcaption>Sample of the first iteration</figcaption></figure><p>We used <a href="https://trello.com/"><strong><em>Trello</em></strong></a> board — a project management software — to easily assign tasks, collaborate and collect notes in a central location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JYCBMyJTeovvRK9CDiLkNQ.png" /></figure><p>I have had to look beyond the normal developer “roles” or “stack” we each were responsible for during this portfolio project. I had to think like a product owner, wear the lenses of a product designer, learn and enforce flow and integration, dive into the backend when necessary, play around with CI/CD and hosting platforms (free or very friendly ones of course, 😂) and become familiar with new frameworks and tools. Familiar enough to build with them from scratch.</p><p>Since this was done as part of the <a href="https://www.alxafrica.com/"><strong><em>ALX-SE</em></strong></a> program, we had the opportunity to present our product to a panel of mentors, from problem definition, through solution concept to deployment. So I learned how to pitch a tech product professionally.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2IHUtb9XMFof2Gl_3atybg.png" /><figcaption>Sample user story from our presentation</figcaption></figure><p>This project made me more aware of how fulfilling I find building stuff from the ground up. It was a lot of work and some terrains were new, but it was worth every effort put in.</p><p><strong>MY JOURNEY FROM HERE ON OUT</strong></p><p>I always believed I lived for business logic and debugging🤣. I still do.</p><p>But, I currently have no absolute reply when asked to choose if I would specialize as a Backend or Frontend Engineer. Truthfully, while I might tend towards the former, I can not deny the exhilaration I got from my role in this project. I want to do all and be involved in all, I want it all!!😂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*YSZ9DbuHtAIoQVFALnlMCg.gif" /></figure><p>Maybe I’ll be lucky enough to get gigs where I can pull a team together to work on so that I will be able to contribute in every aspect or I will be offered roles where I don’t have to entirely sacrifice one for another.</p><p>Meanwhile, I’ll keep building. I am quite excited about the journey ahead.</p><h3>About me</h3><p>I am a unique blend of creativity, bibliophilism, and the desire to learn. I have a background in Architecture and Construction, and I am excited about solving problems.</p><p>OSBH is on <a href="https://github.com/rotex5/OSHB"><strong><em>GitHub</em></strong></a></p><p>Here is the link to the deployed <a href="https://osbh-app-wnc95.ondigitalocean.app/"><strong><em>OS|BH</em></strong></a>, you can test it out. There might be a few glitches here and there. We did just a basic tier hosting, so you might need to reload a few times to load some resources.</p><p>And if the link eventually stops working (I might take it down after a few days), you can check out a video demo <a href="https://www.youtube.com/watch?v=PxuMlrNxoA8"><strong>here</strong></a></p><p>If you’re curious about what I previously built with Flask, It is a very simplified <a href="https://github.com/David-Inkheart/HBNB_V4"><strong>AirBnB clone</strong></a>. The API is served <a href="http://web-01.david-inkheart.tech/api/v1/states"><strong>here</strong></a></p><p>Let’s connect on <a href="https://www.linkedin.com/in/david-okolie"><strong><em>LinkedIn</em></strong></a></p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc8fceb173f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My ALX-SE Learning Journey: The Value of Grit, Community, and Conviction]]></title>
            <link>https://medium.com/@David-Okolie/my-alx-se-learning-journey-the-value-of-grit-community-and-conviction-4011f72c5534?source=rss-6eb69a1f42ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/4011f72c5534</guid>
            <dc:creator><![CDATA[David Okolie]]></dc:creator>
            <pubDate>Wed, 29 Mar 2023 16:30:31 GMT</pubDate>
            <atom:updated>2023-03-29T19:19:52.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sn6UUiDAf1mvinOZ" /><figcaption>Photo by <a href="https://unsplash.com/@jefflssantos?utm_source=medium&amp;utm_medium=referral">Jefferson Santos</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Beginning</h3><p><a href="https://www.alxafrica.com/">ALX </a>is a leading technology training provider, built to accelerate the careers of young Africans through the technology and professional skills that enable them to thrive in the digital economy.</p><p>The <a href="https://www.alxafrica.com/software-engineering/">ALX-SE</a>, a unique software engineering programme, is a rigorous journey that prepares one to succeed in the most high-growth industries. Through the ALX training, one gains the job-ready skills and critical competencies to seamlessly navigate the digital economy and develop skill sets fit for a global career.</p><p>It is a paid programme, but is entirely free for Africans who get past the application process, courtesy of ALX’s partnership with Mastercard.</p><p><strong>My journey has been rigorous, but, I stand firm as it continues, please follow my story…</strong></p><p>I came Across ALX at a time when I definitely wanted more for myself. I had been considering the best way to upskill — be globally relevant, be valuable, and contribute my bit to the world. Then I saw an ALX advert for their program and I applied.</p><p>The application was in April 2022 and it was a soul-searching one. I was convinced it was what I needed while completing the application because of the kind of questions asked that enabled me to put some of my thoughts into writing. Imagine my joy when I got in and started in June 2022, you’d have thought I won the lottery. Well, I did win.</p><p>In the twinkling of an eye, it’s been 9months already! To think that there was a time I did not know the littlest thing about programming. <br> <br> I remember the grit and mindset sessions of June 2022 and boy, did they come in handy. <br> <br> I saw a lot of the hospital that year, my pregnant wife even had to be admitted at some point. Several times, I thought it was time to drop ALX because I had to be fully there for her. <br> One good thing was that I worked freelance, so my time was mostly mine to manage. I pressed on, seemingly against the tides, I relied on friends and mentors to walk me through difficult concepts, and my drive to finish somehow got stronger. <br> <br>When our beautiful daughter came in early November 2022. Amidst the joy, celebration, and gratitude for such a blessing were the thoughts of the reality of nursing a baby girl, being a present husband, working, and learning to be a seasoned Software Engineer. I drew a priority list and almost said goodbye to ALX again and their innumerable and brain-wracking tasks!<br> <br>I’m glad I did no such thing! <br> <br>After thinking about the kind of life I’d love my jewel to have, my drive actually doubled! I made a silent vow to myself to finish the journey, manage my time better and be the best Dad and Full-stack Engineer there ever was! I did not have to choose; I could be all these things! I just needed to know when to wear which hat and wear it well. <br> <br> So I say, may our roads be rough and may hard things never stop coming our way, that we may eventually look back at it all, and be able to chronicle exactly how we <strong><em>transcended</em></strong> and help others do likewise!</p><h3>The Barter System of ALX-SE Programme</h3><p>ALX-SE is a free program for Africans that succeed in their application. You will not have to pay any money.</p><p>But, you will pay.</p><p>Part of the program requirement is dedicating 70hrs per week. This is actually not a scare tactic. I can tell you from experience that sometimes, you will need more than that. I like to approach things with methodology and in an organized manner, so when I started in June, I split the required time into 10hrs a day, 7 days a week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/194/1*B_FhIpDmWFD1H88QGn7oHA.gif" /><figcaption>Insane, right?</figcaption></figure><p>Sometimes, it was barely enough.</p><p>I had to put in even more hours. I once did roughly 20 hours per day for 3days straight. I have been stressed, burnt out, sleep deprived, cranky, annoyed, and just plain fed up while trying to imbibe the knowledge and honestly solve the tasks.</p><p>I can say for certain, it all paid off eventually. As time went by, I got better, learning became a bit easier and the <a href="https://customizinglife.com/feynman-technique/">Feynman learning technique</a> which I encountered in the program was one of the hacks. Just about a month in, I quickly learned another hack and a very important lesson — <a href="https://en.wikipedia.org/wiki/RTFM#:~:text=RTFM%20is%20an%20initialism%20and,forum%2C%20software%20documentation%20or%20FAQ.">RTFM!</a></p><p>Documentations were my friend, not some arduous task I was being forced to do, but an actual lifesaver. So I spent more of the allotted time reading and understanding, before attempting the tasks or puzzles. And it paid off.</p><p>As time went by, we had to get more practical in the program and I realized my edge over many. I complained less and seemed to have it easier or came to a solution more quickly because I started on the right foot — Mindfully understanding the given documentation, searching out more documentation, and watching even more videos till I could give a summary or explain to anyone, in my own words, what the subject matter is about, how it applies to industry use and why I am learning it.</p><p>ALX-SE runs a curriculum that was founded in SILICON VALLEY, the resources were curated by top minds in the industry with the highest standards and best approaches being adopted. It does not promise ease! You will work very smart and very hard.</p><p>The very motto of ALX is “Do hard things”.</p><p>And quoting ALX CEO, Fred Swaniker <em>“I believe that those of us who are privileged enough to be educated, healthy, and part of powerful networks should not be doing easy things”</em></p><p><strong>HOW I WORE MY HATS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HsY7_MZuj8Gb3-El" /><figcaption>Photo by <a href="https://unsplash.com/@stellofello?utm_source=medium&amp;utm_medium=referral">Case Hubbart</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplas</a>h</figcaption></figure><p>Balancing a demanding software engineering program like ALX-SE with freelancing, being a husband, and a father to a baby girl was definitely a challenging task. It required a lot of time management skills, discipline, and sacrifice.</p><p>Here are some specific ways I balanced these responsibilities:</p><p><strong>Prioritizing:</strong> I had to prioritize my tasks based on urgency and importance. I created a to-do list every day and assigned priorities to each task, focusing on the most important and urgent tasks first.</p><p>So my average day went roughly thus: I woke up before anyone at home and shared such early hours between tending to my freelance work and poring through resources for my ALX task because of the quiet. Then Family chores and time with my wife and baby, then back to ALX to read more, watch more videos or solve tasks, a break to watch anime or play video games, solve more project tasks, and spend time with Family in the evening mostly through dinner and when everyone has tucked in, spend some more time on my project and freelance work.</p><p><strong>Time management</strong>: I had to manage my time effectively by making the most of every minute. This meant cutting down on distractions like social media and unnecessary phone calls and focusing on my work and project during my designated work hours.</p><p><strong>Sacrificing leisure time</strong>: I had to sacrifice some of my leisure time, like weekends and evenings, to complete my projects for ALX-SE and my freelancing projects. This was not easy, but it was necessary to meet my goals. I did take the occasionally deserving much-needed break to spend whole weekends with family or just go out for fresh air.</p><p><strong>Support from family and friends</strong>: My wife was very supportive during this time. I also had to communicate effectively about my schedule, so times when I dropped the ball on family time, she patiently reminded me and we had a workaround.</p><p>Friends helped a lot. I once had to keep one up almost all night to help me check where I was going wrong with my code and I realized that taking the time to just talk to friends can be a much-needed respite.</p><p><strong>Staying organized:</strong> Staying organized was crucial. I used tools like calendars, reminders, and an excel sheet to help organize my day and week. I had a note dedicated to the program.</p><p>Overall, balancing ALX-SE, freelancing, and family responsibilities was a tough but rewarding experience. It taught me valuable time management skills and helped me become more disciplined and focused. It also helped me appreciate the importance of support and understanding in achieving anything.</p><p><strong>WHAT YOU INVEST AND HOW IT PAYS OFF:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*l0rDOWbC6BVuchUu" /><figcaption>Photo by <a href="https://unsplash.com/@towfiqu999999?utm_source=medium&amp;utm_medium=referral">Towfiqu barbhuiya</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Investing in oneself is one of the most important things a person can do to achieve success and personal growth. In the case of ALX-SE, <strong>investing time, thought, presence of mind, grit, and gumption</strong> is crucial to succeeding in the program and in one’s career as a software engineer.</p><p>Here are some ways in which investing in oneself through ALX-SE can pay off in the long run:</p><p><strong>Career advancement:</strong> ALX-SE provides practical training in software engineering, which is a highly in-demand skill in today’s job market. Investing time and effort in the program can lead to career advancement and opportunities for higher-paying jobs.</p><p><strong>Personal growth:</strong> The ALX-SE program is not just about learning technical skills but also developing soft skills like teamwork, problem-solving, and communication. These skills can be valuable in all aspects of life and can contribute to personal growth and development.</p><p><strong>Professional network:</strong> ALX-SE provides a community of learners who can provide support, advice, and networking opportunities. Investing time and effort in the program can lead to valuable connections and a professional network that can be useful in the long run.</p><p><strong>Flexibility and adaptability:</strong> ALX-SE teaches learners how to learn and adapt to new technologies and programming languages. This can be useful in an ever-changing job market and can contribute to professional growth and success.</p><p><strong>Personal satisfaction:</strong> Investing in oneself through ALX-SE can provide a sense of personal satisfaction and accomplishment. It can boost self-confidence and self-esteem, which can be valuable in all aspects of life.</p><p>Overall, investing time, thought, presence of mind, grit, and gumption in oneself through ALX-SE can pay off in many ways. It can lead to career advancement, personal growth, a professional network, flexibility and adaptability, and personal satisfaction.</p><h3>The Importance of Community</h3><p><strong>Community is the support framework of ALX-SE</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s5uIG80VTgsYq0E7" /><figcaption>Photo by <a href="https://unsplash.com/es/@shanerounce?utm_source=medium&amp;utm_medium=referral">Shane Rounce</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>One of the most unique and valuable aspects of the ALX-SE program is the community of learners it creates. The program is designed to be collaborative, and learners are encouraged to work together, share ideas, and support one another throughout the program.</p><p>In discussing a group project with a friend who has been in the tech industry for years, who had to learn all by himself and did not wish his experience on anyone else, I will paraphrase his response to ALX community-driven approach:</p><p><em>“Learning how to code is hard, so hard that I, most times, will not encourage anyone to embark on such a journey unless I find they are already on it and they know what they are getting into, then I will spur them on.</em></p><p><em>It is a good thing you have a community to do this journey together with. It makes it easier, it can make all the difference”</em></p><p>Here are some ways in which the ALX-SE program created a community of learners who supported each other:</p><p><strong>Group Projects:</strong> The program includes group projects that require learners to work together and collaborate to complete a project. This helps learners develop teamwork and communication skills and fosters a sense of community and collaboration.</p><p><strong>Peer Review:</strong> Learners are encouraged to review and provide feedback on each other’s work, which creates a culture of peer review and constructive criticism. This helps learners improve their work and also provides opportunities for learners to learn from each other.</p><p><strong>Mentorship:</strong> The program includes mentorship from experienced software engineers who provide guidance and support to learners throughout the program. This helps learners feel supported and connected to a larger community of professionals.</p><p><strong>Peer Learning Days(PLD):</strong> The program includes days dedicated to virtually meeting and going through projects together. Learners can ask questions, share ideas, and seek help from their peers. This creates a supportive online community where learners can connect and collaborate.</p><p>It was from this initiative that I made 4 friends — George, Paul, Philip, and Davidson — with who I have learned and collaborated severally with to navigate the difficulties of the program.</p><p>I connected with George over slack in our first month of ALX in June 2022. We both have Architectural backgrounds and became instant friends.</p><p>We decided to have our own PLD group and keep it at a max of 5 people, small enough to build a good relationship with everyone, and large enough to have many driven minds pooled together. George brought in Paul.</p><p>I met Philip in an ALX-intranet PLD I decided to anchor and was glad when he showed his interest in the private PLD we had. So he joined us. Then he brought in Davidson.</p><p>Each of these amazing guys has been extremely instrumental in my journey and growth in Software Engineering so far.</p><p><strong>George</strong> always pushed that we met as a group and went through what we learned together, in more ways than one, he held the group together and always brought in spicy topics and banters.</p><p>Thank you, George, I think I can say on behalf of all of us, we kept on being connected because of you.</p><p><strong>Philip</strong> taught me pointers in C. I had a bit of a tough time with that concept, but he somehow got it and was able to break it down in a way I grasped. So whatever mastery I might seem to have over every other topic that needs a knowledge of pointers, such as structs, linked lists, binary trees, etc… I thank Philip for his help.</p><p><strong>Davidson</strong> in a way is the life of the party. He laughs at everything and everyone. He makes learning seem easy and fun and always somehow has a link to any resource needed to solve any issue. He somehow has a knack for easy ways to solve complex problems. He is our personal daily digest of what is happening in the tech world.</p><p>Thank you!</p><p><strong>Paul</strong> is a repository of all things C. At a time when we were all getting tired and frustrated of the language and segmentation faults almost ran us bald, Paul’s love for the language was both annoying and refreshing. Davidson took out time daily to ‘drag’ him about it or tag him in funny memes about C.</p><p>Of course, he spearheaded a lot of discussions on topics in C. It’s his niche after all.</p><p>A big thanks to you for spurring us on!</p><p>Overall, the ALX-SE program creates a community of learners who support each other through collaboration, peer review, mentorship, and peer learning days. This community helps learners feel supported, connected, and engaged throughout the program and provides valuable networking opportunities for the future.</p><h3>Handling Impossible Tasks and Roadblocks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wrm1ooEvxQWZWrXo" /><figcaption>Photo by <a href="https://unsplash.com/@kazheard?utm_source=medium&amp;utm_medium=referral">Joel Heard</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The ALX-SE program is a demanding program that requires a lot of time and effort from learners. As someone without prior coding experience, I faced several challenges during the program, including tutorial hell and documentation overload.</p><p>Tutorial hell or documentation overload refers to the feeling of being overwhelmed by the number of tutorials, resources, or documentation available for learning about programming concepts and tools. Documentation is essential for understanding new concepts and how to use new tools, but it can be tedious and time-consuming to read through. In the ALX-SE program, I experienced this a lot, and it was easy to feel lost in the sea of tutorials and resources available online.</p><p>Here are some ways in which I overcame these challenges:</p><p><strong>Prioritization:</strong></p><p>I was so caught up with the novelty of the whole learning experience that I chased down any resource that remotely had to do with each concept. While this is good and should be encouraged when learning something new, soon, I realized I was running down a rabbit hole as one concept quickly and easily led to another. I realized chasing extra resources should not be done at the expense of what one is supposed to actually learn per time. I learned to prioritize the resources and documentation that were most relevant to the project I was working on at that time. This helped me avoid getting lost in tutorial hell and focus on the concepts, tools, and skills that were most important.</p><p><strong>Time Management:</strong></p><p>I learned to manage my time effectively, setting realistic goals for what I could accomplish each day and week. This helped me avoid feeling overwhelmed by the amount of work required. Sometimes I left advanced tasks undone till I had the time to later return to them, sometimes, I boycotted optional tasks till I had the time to return to them.</p><p><strong>Support from the Community:</strong></p><p>I and the other four guys shared tips and resources, provided feedback on each other’s work, and helped each other troubleshoot problems. Doing this program alone will almost always lead to frustration. You need all the help you can get and sometimes while giving help or teaching someone else the little you think you know about a concept, that concept settles deeper, or ideas to solve some hanging tasks can pop up.</p><p><strong>Breaks and Self-Care:</strong></p><p>It is important to take breaks and practice self-care when facing challenges, rather than quit altogether. I made sure to take breaks when I felt overwhelmed and engaged in activities that helped me relax and recharge. I sometimes took the whole weekend off, sometimes weekdays. What that difficult task or problem needs might just be a well-rested and relaxed mind. So step back, sleep, go for a stroll, watch a movie, do anything else, and come back to the issue with fresh eyes and mind.</p><p>Now, one can even pause the program for a whole month if absolutely necessary.</p><p><strong>Funny story:</strong> I once could not solve a scripting task. It gave me a headache. I went to bed early that night, had a nightmare about “#!” and woke up with the solution to the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*nCYmFZnGRzHYFyb6LfL9Zw.gif" /></figure><h3>Conviction and Purpose</h3><p>I knew exactly what I wanted and why I enrolled in the ALX-SE programme. I came in very convinced and motivated, and my conviction drove me when I would have thrown in the towel.</p><p>I reminded myself why I was doing this, what I hoped to achieve, and how far I had come.</p><p>In the face of the humungous work to do and concepts to learn, imposter syndrome set in severally. I realized it was normal, and I got moving by reminding myself why I chose this path and how well I had done so far. I told myself I did it, I have all the help and resources I need, and I will keep relying on them to keep doing it.</p><p>One thing that has solidified in the very core of my being is that we are all capable of far beyond what we allow ourselves to handle and sometimes, only the strength of conviction in the face of hardship will force a transcendence from the pedestrian. So,</p><p>let our roads be the roughest,</p><p>let things we do be the hardest,</p><p>We must soar, run, walk, crawl, slink,</p><p>Through the rough roads, never blink,</p><p>By any means, we’ll keep moving ahead,</p><p>We’ll transcend and rise, like the sun we’ll spread.</p><h3>Now,</h3><p>As you embark on your learning journey, ALX-SE program, or any other, remember to prioritize relevant resources, manage your time effectively, seek support, practice self-care, maintain conviction and purpose, and trust in your abilities. With these tips in mind, you can overcome the challenges of learning a new skill and achieve the success you desire.</p><p>To cap it all up, it is not enough to desire the trendiness of tech or the possibility of cool cash to succeed in the ALX-SE program. It is the conviction of purpose, an insane drive to upskill, and a genuine desire to solve problems and add value to society that constitutes the recipe for a successful journey doing hard things.</p><p>My experience so far in the ALX-SE programme has been an interplay of grit, community, and conviction. Roughly 9 months ago, I had zero knowledge about coding or building stuff as a Software Engineer, or about the trends of the tech industry. Now, I can solve real-world problems as a Full-stack Software Engineer using diverse programming languages and stacks.</p><p>You can do it too. You can do more!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4011f72c5534" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What happens when you type "https://www.google.com” in your browser and press "Enter”.]]></title>
            <link>https://medium.com/@David-Okolie/what-happens-when-you-type-https-www-google-com-in-your-browser-and-press-enter-987c2b47bbaf?source=rss-6eb69a1f42ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/987c2b47bbaf</guid>
            <dc:creator><![CDATA[David Okolie]]></dc:creator>
            <pubDate>Fri, 27 Jan 2023 19:44:12 GMT</pubDate>
            <atom:updated>2023-01-31T07:17:26.955Z</atom:updated>
            <content:encoded><![CDATA[<h3>What happens when you type https://www.google.com in your browser and press Enter.</h3><figure><img alt="Robotically updraded you typing furiously on your futuristic laptop and your minions scuttling around to work" src="https://cdn-images-1.medium.com/max/1024/1*Iu-kDHxsMzWKQX2TYaTY7A.png" /></figure><p>When you type “<a href="https://www.google.com/">https://www.google.com</a>&quot; into your browser and press “enter”, a series of events are set in motion that eventually lead to the website being displayed on your screen.</p><p>First, the browser sends a request to the Domain Name System (DNS) to resolve the domain name “google.com” to an IP address.</p><h4><strong>The Domain Name System</strong></h4><p>The DNS is a hierarchical and decentralized system that is responsible for translating domain names, such as “google.com,” into IP addresses. IP addresses are a series of numbers, such as “172.217.162.174,” that are used to identify devices on a network, and since humans are generally bad at remembering lengthy numbers ( try memorizing <a href="https://en.wikipedia.org/wiki/Euler%27s_constant">Eular’s constant</a> if you disagree), you type “<a href="https://www.google.com/">https://www.google.com</a>&quot; into your browser instead of the actual IP address of Google, the browser sends a request to the DNS to resolve the domain name “google.com” to an IP address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xa2e0S4GOX_NzE3WQ8Atvg.jpeg" /></figure><p><em>Here are the hierarchies:</em></p><p>This process starts with the browser checking its<strong> local cache</strong> to see if it already has the IP address for the domain name. If the IP address is not found in the cache, the browser sends a request to the <strong>local DNS resolve</strong>r, which is typically provided by the internet service provider (ISP). The local DNS resolver checks its cache and, if the IP address is not found, it sends a request to the root name server.</p><p><strong>The root name server</strong> is the top-most level of the DNS hierarchy and is responsible for directing the request to the appropriate top-level domain (TLD) name server. For example, the TLD for “google.com” is “.com,” so the request is directed to the “.com” TLD name server.</p><p><strong>The TLD name server</strong> then directs the request to the appropriate authoritative name server. The authoritative name server is responsible for maintaining the information for a specific domain, in this case, “google.com.”</p><p><strong>The authoritative name server</strong> then responds with the IP address associated with the domain name. This IP address is then cached by the local DNS resolver, and the browser uses this IP address to establish a connection with the server.</p><p>It’s important to note that DNS requests are not only limited to web pages but are also used for other services like email, instant messaging, and other internet services.</p><p>It is also worth mentioning that different types of DNS records can be used for different purposes, like <strong>A record</strong> for IPv4 addresses and <strong>AAAA record</strong> for IPv6 addresses, <strong>CNAME record</strong> for aliases, and <strong>MX records</strong> for email servers.</p><p>DNS generally, is like a phonebook for the internet, it maps domain names to IP addresses. Once the IP address is obtained, the browser establishes a connection with the server using the Transmission Control Protocol (TCP) and the Internet Protocol (IP). This process is commonly referred to as the TCP/IP handshake.</p><p><em>Next up in this amazing journey of your request is the TCP/IP:</em></p><h4><strong>TCP/IP</strong></h4><p><a href="https://www.avast.com/c-what-is-tcp-ip#:~:text=TCP%20and%20IP%20are%20two,difference%20between%20TCP%20and%20IP.">TCP/IP</a> stands for Transmission Control Protocol/Internet Protocol. TCP/IP is a set of standardized rules that allow computers to communicate on a network such as the internet.</p><p>A <strong>protoco</strong>l is an agreed-upon set of rules. In human terms, we use social protocols to know how to behave and communicate with other people, It’s the same thing with computers, but with more hard-and-fast rules. When computers all use the same protocol, information can be transferred.</p><p>The <strong>IP addres</strong>s is like the phone number assigned to your smartphone. TCP is all the technology that makes the phone ring, and that enables you to talk to someone on another phone. They are different from one another, but they are also meaningless without one another.</p><p><strong>The TCP/IP handshake</strong> is the process that establishes a connection between two devices or software on a network, such as a web browser — the application software you are typing the website into, e.g. Chrome, Safari, etc.) and the server — the guys on the other end serving you the google webpage. It involves a series of messages exchanged between the devices to initiate, acknowledge, and confirm the connection.</p><p><strong>TCP/IP breaks each message into <em>packets</em></strong>, and those packets are then reassembled on the other end. In fact, each packet could take a different route to the other computer, if the first route is unavailable or congested. This way, if the message were to encounter a problem, the whole message would not have to be re-sent, just the bits that went AWOL. It is a reliable connection, which means that packets are acknowledged, and retransmission of lost packets occurs, this makes sure that the data is delivered and received correctly. <em>Cool, right!?</em></p><h3><strong>Firewall</strong></h3><p>Next, the request is passed through any firewalls that may be present to ensure that only authorized traffic is allowed to pass through. Firewalls act as a barrier between a private internal network and the public internet.</p><p><strong>A firewall</strong> is a security system that controls the incoming and outgoing network traffic based on a set of predefined rules and policies. The main purpose of a firewall is to prevent unauthorized access to a private network and to protect the network from malicious attacks. Before the request is passed on to the server, it needs to pass through the firewall which uses use the IP address and port number of the packets to determine if they should be allowed to pass through or not.</p><p>The firewall inspects the incoming request, compares it against its set of predefined rules, and decides whether to allow or block the request. The rules are usually set up by network administrators and can be based on various parameters such as IP addresses, port numbers, and protocols.</p><p>For example, a firewall rule might specify that only incoming requests from a specific IP address range are allowed, or that incoming requests on a specific port number are blocked.</p><p>If the request is deemed to be safe, the firewall will allow it to pass through to the server. If the request is deemed to be unsafe, the firewall will block it, preventing the request from reaching the server.</p><p>Once the request has passed through the firewall, it reaches the server, which is likely to be behind a load balancer. A load balancer is a device or software that distributes incoming traffic across multiple servers to ensure that no single server is overwhelmed.</p><h3><strong>Load Balancers</strong></h3><p>Load balancers are typically used in high-traffic websites (just like the one you requested) and web applications to ensure that the service remains available and responsive even under heavy load. They are typically software or hardware that handle the job of distributing duties or workloads fairly to the actual servers dishing up the request, according to the amount of traffic available and a preset algorithm (logic or method of distribution).</p><p>The load balancer then passes the request on to the appropriate server, which is responsible for handling the request and returning the appropriate files to the browser, in this case, the web server is likely to be serving up the HTML, CSS, and JavaScript files that make up the Google homepage.</p><h3><strong>Servers</strong></h3><p><strong>The </strong><a href="https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_is_a_web_server"><strong>web server</strong></a> is responsible for interpreting the request and determining the appropriate action to take. The web server uses the information in the request from the client (you and your browser), such as the URL — the google address you typed into your browser, and any query parameters (any additional specific search you run or want from google), to determine which files should be returned to the browser.</p><p>In the case of the Google homepage, the web server is likely to be serving up the HTML, CSS, and JavaScript files that make up the webpage. The HTML files contain the structure and content of the webpage, the CSS files contain the styling information, and the JavaScript files contain any interactive functionality.</p><p>When the web server receives the request, it looks up the requested URL in its file system or database and retrieves the appropriate files. The web server then compiles these files, applies any server-side logic that may be required, and sends the resulting HTML code back to the browser.</p><p>Google uses its own in-house developed web server called <a href="https://en.wikipedia.org/wiki/Google_Web_Server">Google Web Server (GWS)</a> — a custom Linux-based Web server. It is proprietary <a href="https://en.wikipedia.org/wiki/Web_server">web server</a> software that <a href="https://en.wikipedia.org/wiki/Google">Google</a> uses for its web infrastructure. GWS is used exclusively inside Google’s ecosystem for website hosting. In 2010, GWS was reported as serving 13% of all websites in the world!</p><p><em>Amazing!!</em></p><p>The web server can also be responsible for generating dynamic content. For example, the web server can access a database to retrieve data that is specific to the user making the request and include it in the HTML code that is returned to the browser.</p><p>The term <em>dynamic</em> means that the server processes the content or even generates it on the fly from a database</p><p>There is no official data on how many <a href="https://en.wikipedia.org/wiki/Server_(computing)">servers</a> are in Google data centers, but <a href="https://en.wikipedia.org/wiki/Gartner">Gartner</a> estimated in a July 2016 report that Google at the time had 2.5 million servers. This number is changing as the company expands its capacity and refreshes its hardware.</p><p><em>Now back to your request:</em></p><p>The request may also be passed on to an application server, which is responsible for running any server-side code that may be required to generate the dynamic content on the page.</p><p><strong>An application server</strong> is a type of server that is specifically designed to run server-side code and provide an environment for executing the code. An application server is typically used in web applications to handle tasks such as processing user input, connecting to databases, and generating dynamic content.</p><p>In the case of the Google homepage you requested, Google likely uses its application server to serve the doodles on its homepage. Doodles are dynamic images that are often used to commemorate special events or notable people, and they are frequently changed on the homepage.</p><p>To generate and serve these dynamic images, the application server would likely use server-side code to retrieve the appropriate image or images from a database or file system, and then apply any necessary transformations or animations to the image before sending it back to the web server. The web server would then include the image in the HTML code that is sent to the browser.</p><p>It’s also worth noting that Google is a huge company, it uses a variety of technologies and architecture, and the way the doodles are implemented may be different depending on the specific situation.</p><p>It’s also possible that Google is using a Content Delivery Network (CDN) service to serve the doodles, which are cached on multiple servers in different locations around the world, this will speed up the loading of the doodles as it will reduce the distance the data has to travel to reach the end-user(you) and will help to distribute the load on the servers.</p><p>In any case, Google is tight-lipped about its inner workings and implementation of things like its doodles, so these are my assumption based on research and common web development practices.</p><h3>Database</h3><p>Finally, the request may be passed on to a database to retrieve any data that may be required to generate the content. A database is a collection of data that is stored and organized in a specific way to make it easy to retrieve, update, and manage. Databases are typically used to store information such as user information, product information, and other types of data that are required to generate the content of a webpage.</p><p>When the application server receives the request, it may need to retrieve data from a database to generate the dynamic content of the page. The application server would use the appropriate database management system (DBMS) software to connect to the database and retrieve the data.</p><p>For example, when you perform a search on Google, the application server would use the keywords provided by the user to query the database and retrieve the relevant search results.</p><p>It’s worth noting that the way the application server retrieves the data from the database may depend on the specific database management system and the programming language that the application server is written in.</p><p>Additionally, Google would also use a caching system, to store frequently used data in faster storage so it can be retrieved quickly and reduce the load on the databases.</p><p>In summary, the database plays a crucial role in storing and managing the data that is required to generate the content of a webpage, and it works in conjunction with the application server to retrieve and use this data to generate dynamic content.</p><p><strong><em>Did you notice that when requesting the webpage, it started with “https”?</em></strong></p><p><strong><em>Ever wonder why?</em></strong></p><h3><strong>HTTPS/SSL</strong></h3><p>Usually, when the packets are being transmitted between computers, they are vulnerable to being seen by others. That’s one reason why you are advised to avoid public Wi-Fi networks when sending data that must stay private, and to use <a href="https://www.avast.com/c-how-to-turn-on-wifi-encryption-in-your-router-settings">encryption</a>.</p><p>It’s important to note that the “https” in the URL (https://www.google.com), indicates that the connection is secure and encrypted using Secure Sockets Layer (SSL) or its successor Transport Layer Security (TLS), this is to ensure that the information exchanged between the client (you) and the server (Google’s server) is private and secure.</p><p>This is done to make sure that the information exchanged between your browser and the Google server is private and secure.</p><p>Think of it like a secret code that only your browser and the Google server can understand, this way if someone intercepts the information sent between the two, they won’t be able to read it.</p><p>This encryption is important because it helps to protect sensitive information, such as login credentials, credit card numbers, and personal information from being intercepted and read by unauthorized parties.</p><p>Additionally, the <a href="https://www.instantssl.com/http-vs-https">SSL/TLS</a> certificate, which is provided by a trusted third-party called a certificate authority, is used to verify that the website you are visiting is an authentic website and not a fake one trying to steal your information.</p><p>Concisely, the “https” in the URL indicates that the connection between your browser and the Google server is secure and encrypted, which helps to keep your personal information private and protected from unauthorized access.</p><h3>Conclusion</h3><p>The process of typing “<a href="https://www.google.com/">https://www.google.com</a>&quot; into a browser and pressing “enter” may seem simple, but it involves a complex series of events to ensure that the information exchanged is safe, secure, and fast.</p><p>All of these steps happen in a matter of milliseconds, allowing you to quickly and easily access the website you requested.</p><p><em>I hope this post was helpful in understanding the underlying technology involved in browsing the internet.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQISEs8l8XOpTcjoJH8jNQ.jpeg" /><figcaption>Please note that this Illustration is a very rough and very simplified representation of the process and does not contain all the details, thus is not a functional diagram or annotation, but it should give you a general idea of what happens when you type “<a href="https://www.google.com/">https://www.google.com</a>&quot; into your browser and press enter.</figcaption></figure><p>If you’re interested in something similar like “What Happens Inside Your Computer When a Key is Pressed?” check <a href="https://www.futurelearn.com/info/courses/computer-systems/0/steps/53503">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=987c2b47bbaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GO FRONT SMALL, E NO FAR]]></title>
            <link>https://medium.com/@David-Okolie/go-front-small-e-no-far-fce16fbf280b?source=rss-6eb69a1f42ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/fce16fbf280b</guid>
            <dc:creator><![CDATA[David Okolie]]></dc:creator>
            <pubDate>Thu, 28 Mar 2019 09:51:49 GMT</pubDate>
            <atom:updated>2019-03-28T09:51:49.202Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*bq_T1AJkzNXheUGPktoI1g.jpeg" /></figure><p>GO FRONT SMALL, E NO FAR</p><h3>(It is just ‘round the corner)</h3><p>If you have had the fortune (some might say misfortune) of asking a lagosian in Nigeria for direction to a particular place, especially if you already were made to believe it&#39;s a walkable distance, the expression &quot;go front small, e no far&quot; shouldn&#39;t be very strange.</p><p>Some of those people we use as way-markers might mislead or misdirect, having poor description skills or an inadequate idea of our destination. But, I sincerely believe some have walked that route long enough and have come to know it intimately, that to them, &quot;e no far&quot; is no longer a big deal.</p><p>For a stranger to such path, once you start that same journey of &quot;e no far&quot; you&#39;d quickly realise it might be farther than was communicated. Even after such realisation, while still trudging along the deceptively annoying lengthy road, with a sheen of glistening sweat on the forehead, ankles and knees protesting slightly, especially if you&#39;re not one for long walks, and you still need to be sure you&#39;re on the right track, you would decide to ask someone else who might end up telling you the same - &quot;go front small, e no far&quot;</p><p>I have come to think about it this way, one who&#39;s been on that terrain for long sees the trek easier and faster than one who&#39;s new/green to that same area. Their concept of distance to destination is different. And for the newbie, after taking that same route a few times, you&#39;d realise that the destination was never too far, just a bit more and you always arrived.</p><p>The interesting thing is, however annoying these unsure pointers are, you would never know how far or close you are if you get frustrated and don&#39;t move forward a bit more - don&#39;t go on - and decide to stop or turn back. You would need to reach the end and experience the journey yourself , only then would you have your own perfect description.</p><p>Sincerely, this is very similar to our endeavours in life. We tend to easily get frustrated after our long distance strivings have yielded naught, but more pointers forward. <br>It would be a tragedy to flag then stop, mere inches from the desired finish. <br>A little more belief. <br>A little more push. <br>A little more smile. <br>A Little more song.<br> A little more dance.</p><p>Go front small, e no far.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fce16fbf280b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>