<?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 OLACHI ROSEBUD OKERE on Medium]]></title>
        <description><![CDATA[Stories by OLACHI ROSEBUD OKERE on Medium]]></description>
        <link>https://medium.com/@olachiokere1995?source=rss-6e1dc1e76a32------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*caFdB964AHaVUpEM</url>
            <title>Stories by OLACHI ROSEBUD OKERE on Medium</title>
            <link>https://medium.com/@olachiokere1995?source=rss-6e1dc1e76a32------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 12:15:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@olachiokere1995/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[Weeks 4 & 5: My Research Journey — From an Idea to a Research Proposal]]></title>
            <link>https://medium.com/@olachiokere1995/weeks-4-5-my-research-journey-from-an-idea-to-a-research-proposal-834255b98d08?source=rss-6e1dc1e76a32------2</link>
            <guid isPermaLink="false">https://medium.com/p/834255b98d08</guid>
            <dc:creator><![CDATA[OLACHI ROSEBUD OKERE]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 23:40:01 GMT</pubDate>
            <atom:updated>2026-10-13T23:40:01.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e7UYsRZNBGy3ZLLc" /><figcaption>Photo by <a href="https://unsplash.com/@duforddigital?utm_source=medium&amp;utm_medium=referral">MJ Duford</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If there is one thing these past two weeks have taught me, it is that choosing a research topic is not just about picking something interesting. It is about identifying a problem that can be investigated, understanding why it matters, and figuring out how to study it.</p><p>My research journey started with my interest in women’s health and financial independence. As a Public Health graduate, I have always been interested in how women’s financial situations affect their access to healthcare. I have seen situations where women have to consider their family’s needs before their own health, where financial circumstances affect who makes decisions about their healthcare, and where women who gained financial independence experienced improvements in their health outcomes.</p><p>These experiences made me wonder whether better access to financial services could make a difference in the healthcare decisions women make.</p><p>This led me to my first proposed topic: Digital Financial Inclusion, Digital Health Literacy and Healthcare-Seeking Behavior Among Women in Nigeria.</p><p>I was excited about the idea because it connected two areas I care about: women’s health and financial inclusion. However, the feedback I received from my mentor made me realize that having an interesting idea was not enough. My research problem was not clearly defined, and my approach needed to be more specific.</p><p>I was disappointed, especially because I had put thought into the idea, but the feedback also pushed me to look at my topic more critically.</p><p><strong>Choosing My Research Topic Again</strong></p><p>Instead of abandoning the general area I was interested in, I went back to the drawing board. I began to think about a more specific question: could women’s access to financial services be related to their ability to obtain health insurance?</p><p>That question led me to my revised topic:</p><p>“The Relationship Between Digital Financial Inclusion and Health Insurance Uptake Among Women in Nigeria.”</p><p>This felt more specific and gave me a clearer direction. I could identify the variables I wanted to examine, the population I was interested in, and the data source I could use.</p><p>While searching online for similar studies, I came across the 2024 Nigeria Demographic and Health Survey (NDHS). It appeared to offer relevant information on women, health insurance and selected financial inclusion indicators. Finding a suitable dataset was an important step because I needed a research question I could actually investigate with the information available.</p><p><strong>The Challenges</strong></p><p>One of my biggest challenges was the methodology. I needed to understand which variables to use, how to analyze them, and how to make sure the analysis matched my research question.</p><p>Then came the data analysis itself. I had not used SPSS in years, and I did not have access to it. Although I had some previous exposure to data analysis, working with a large DHS dataset was a different experience.</p><p>The dataset contained thousands of variables, and identifying the ones relevant to my study was initially overwhelming. I also had to learn about sampling weights, strata and clusters. These were important because the NDHS uses a complex sampling design, meaning I could not simply analyze the data as though every respondent had been selected in the same way.</p><p>On top of that, I had no previous experience with R. Trying to learn a new tool while also understanding the data and deciding how to analyze it felt overwhelming at times. There was a lot to take in, and I had to remind myself that I did not need to understand everything at once.</p><p><strong>Lessons Learnt</strong></p><p>I learned to break the process into smaller steps instead of trying to figure everything out at once. I started by identifying the variables that matched my research questions. Then I worked on understanding the dataset, checking how the variables were coded, and preparing the data for analysis.</p><p>I continued learning R because it is free and supports the type of survey analysis required for my study. I worked through the process step by step, including setting up the survey design and understanding how the weights, strata and clusters fit into the analysis.</p><p>These two weeks also taught me a few important lessons.</p><p>A good research topic needs to be specific. An idea can be interesting, but I still need to define exactly what I want to investigate and how I intend to do it.</p><p>Feedback is part of the process. Having my initial proposal questioned left me disappointed and shocked at first, but I learned that feedback can help me see the weaknesses in my work and find a clearer direction. I did not have to abandon my interest; I had to refine my approach.</p><p>Research must be practical. I had to consider the availability of data, the variables I could measure, and the methods I could realistically use before moving forward.</p><p><strong>Looking Ahead</strong></p><p>What began as an interest in women’s health and financial independence has gradually developed into a research proposal.</p><p>The journey was not as straightforward as I expected. I had to rethink my original proposal, learn unfamiliar technical concepts, and work through challenges with the data and analysis. But each stage helped me understand my research better.</p><p>I would not say that I now know everything about research, but I have a better understanding of the process and of what I still need to learn.</p><p>I am looking forward to continuing my research on digital financial inclusion and health insurance among women in Nigeria. I also want to improve my knowledge of R, become more confident in defending the methods I use, and get better at explaining my findings in simple terms.</p><p>Beyond this particular research project, I hope to keep building my skills at the intersection of public health and data science. I want to use data not just to describe problems, but also to generate evidence that can support better decisions and practical solutions.</p><p>My Weeks 4 and 5 have reminded me that research is a process of asking questions, receiving feedback, learning, correcting mistakes, and trying again.</p><p>I am still learning, but I am proud of the progress I have made so far. And I am looking forward to seeing where the next stage of this journey takes me.</p><p>One step at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=834255b98d08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3: Handling Errors, Working with Data, and Setting up My Environment Again…]]></title>
            <link>https://medium.com/@olachiokere1995/week-3-handling-errors-working-with-data-and-setting-up-my-environment-again-cef127480939?source=rss-6e1dc1e76a32------2</link>
            <guid isPermaLink="false">https://medium.com/p/cef127480939</guid>
            <dc:creator><![CDATA[OLACHI ROSEBUD OKERE]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 20:12:23 GMT</pubDate>
            <atom:updated>2026-09-27T20:12:23.307Z</atom:updated>
            <content:encoded><![CDATA[<p>This week felt a little different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5iosyzxAxQtVGfH6_VmsYA.png" /></figure><p>It felt like a breather. Not because everything suddenly became easy, but because I was beginning to feel a little more comfortable with Python. The concepts were still new, and there were still moments when I had to stop and go back, but this time, I didn’t feel quite as overwhelmed.</p><p>And honestly, I needed that.</p><p><strong>Welcome to Week 3</strong></p><p>This week, we learnt about modules, date and time, math, JSON, pip, user input, error handling, virtual environments, reading and writing files, and had an introduction to SQL.</p><p>We also had tasks, assignments, and an assessment to put what we were learning into practice.</p><p>Some of the topics were easier to grasp than others, but overall, the week felt more manageable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ox0snbM1qOP2ydh-62Mw1w.png" /></figure><p>One of the things I enjoyed most was working with date and time. Building a Date Calculator was interesting because I got to see how the concepts could be applied to something practical.</p><p>Then there was the Math Quiz Program, which was probably one of my favourite tasks this week. It was satisfying to see different concepts come together to create something that actually worked.</p><p>I also built an Error Handling System and worked on JSON file handling.</p><p>And once again, I was reminded that there is a difference between knowing what a concept means and actually knowing how to use it.</p><p>Although the week felt easier overall, there were still a few concepts that challenged me.</p><p>I struggled with `try`, `except`, `else`, and `finally`. Understanding how they worked together and knowing when to use each one took some practice.</p><p>JSON was another concept I had to spend a little more time on.</p><p>But unlike the beginning of the internship, I’m starting to understand that struggling with a concept doesn’t mean I’m not learning. Sometimes, I just need to slow down, practise, and give myself time to understand it.</p><p><strong>Understanding Virtual Environments</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*XaHLDFxiPFYejuorolL7wQ.png" /></figure><p>One thing that stood out to me this week was creating a virtual environment again.</p><p>We had already done this during the initial setup of our tools and development environment at the beginning of the internship. At the time, however, I was mostly following the instructions just to get everything set up.</p><p>This time, I understood it better.</p><p>I now have a clearer idea of why virtual environments are important and how they help keep project dependencies isolated. We also learnt about pip, which is used to install and manage Python packages. I went a step further by using pip within the virtual environment to install packages such as requests and numpy. This helped me understand the connection between virtual environments and packages better. I wasn’t just learning what a virtual environment was in theory; I was actually using one to manage the packages I needed for my work.</p><p>It may seem like a small thing, but for me, it was a reminder that learning sometimes means looking at something you’ve seen before and finally understanding it.</p><p>I’m beginning to enjoy Python more. There is still a lot I don’t know, and I’m sure the coming weeks will bring new challenges.</p><p>But I’m also beginning to feel a little more confident about facing them.</p><p>Week 3 was a breather.</p><p>And I’m grateful for it.</p><p>Still learning. Still growing. Still taking it one step at a time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cef127480939" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2: When Things Started Getting Real]]></title>
            <link>https://medium.com/@olachiokere1995/week-2-when-things-started-getting-real-b74c211b4ef6?source=rss-6e1dc1e76a32------2</link>
            <guid isPermaLink="false">https://medium.com/p/b74c211b4ef6</guid>
            <dc:creator><![CDATA[OLACHI ROSEBUD OKERE]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 20:28:49 GMT</pubDate>
            <atom:updated>2026-09-20T20:28:49.311Z</atom:updated>
            <content:encoded><![CDATA[<p>If Week 1 was about taking the first step, then Week 2 was about realizing that this journey was not going to be as easy as I thought.</p><p>This week has been very overwhelming. The concepts seemed more difficult. The course outline looked confusing. I would read something, think I understood it, and then try to apply it only to realise that I actually didn’t understand it as much as I thought I did.</p><p>So what did I do? I read it again. And again. And again.</p><p>At some point, I honestly became frustrated.</p><p>But then I reminded myself of the mantra I started this journey with: <strong>One step at a time.</strong></p><p>So, I went back again.</p><p><strong>Welcome to Week 2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*O7z-kheyOfKQHyjvSSGPPw.png" /></figure><p>Week 2 introduced us to <strong>Object-Oriented Programming (OOP) in Python</strong>, and honestly, this was where things started getting really serious.</p><p>The course outline covered quite a number of concepts, including classes and objects, methods, the self parameter, class properties, class methods, magic methods, inheritance, polymorphism, encapsulation, iterators, scope, and other related concepts.</p><p>Reading the list alone looked manageable. Understanding and actually applying them? That was a completely different story. At first, most of these concepts just didn’t make much sense to me.</p><p>I would read the materials and try to follow along with the examples, but sometimes I would get to the end and realise that I couldn’t properly explain what I had just read.</p><p>So I started doing something that became almost a routine this week.</p><p><strong>Read. Practice. Make a mistake. Get frustrated. Go back. Read again. Try again.</strong></p><p>And slowly, gradually, things started becoming clearer.</p><p><strong>Getting Familiar with OOP</strong></p><p>One of the biggest things I learnt this week was how Python uses Object-Oriented Programming to structure code.</p><p>I learnt about <strong>classes and objects</strong>, and how a class can serve as a blueprint for creating objects.</p><p>I learnt about <strong>methods</strong> and how they allow objects to perform certain actions.</p><p>Then there was the self parameter, which initially had me asking myself, <em>“Why do I even need to write this?”</em></p><p>But as I kept practising, I started understanding that self gives an instance access to its own attributes and methods.</p><p>I also learnt about <strong>class properties and class methods</strong>, and how they differ from properties and methods that belong specifically to an individual object.</p><p>Then came the concepts that really made me sit down.</p><p><strong>Inheritance.</strong></p><p><strong>Polymorphism.</strong></p><p><strong>Encapsulation.</strong></p><p>And of course, <strong>magic methods</strong>.</p><p>These were not concepts I could just read once and immediately understand.</p><p>I had to keep going back to them.</p><p>I watched YouTube videos. I searched different websites. I looked for simpler explanations and different examples because sometimes, the way one person explained a concept didn’t make sense to me, but another explanation suddenly made something click.</p><p>And that taught me something important; Sometimes, you don’t need to give up on a concept. You just need to find another way of looking at it.</p><p><strong>Lessons From This Week</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*Q3EzlddecGAtYiODUHvZvg.png" /></figure><p>One major lesson from this week is that understanding doesn’t always happen immediately.</p><p>There were times I felt like I wasn’t making progress because I kept reading the same concepts over and over again. But looking back, I actually was.</p><p>The first time I read about some of these concepts, they looked completely confusing. After seeing more examples and practising them repeatedly, I started recognising the patterns. I started becoming more familiar with the way the code was structured. I started understanding why certain things were written the way they were. It was more like little pieces gradually coming together. And I think that’s what learning something new really looks like sometimes.</p><p>Not knowing. Trying. Failing. Trying again.</p><p>And eventually, understanding a little more than you did yesterday.</p><p><strong>The Challenges — This Week Really Tested Me</strong></p><p>If I’m being completely honest, this week was <strong>challenging</strong>.</p><p>I struggled with understanding the concepts. There were moments when I was just staring at my laptop, looking at the code and wondering what exactly I was supposed to be doing. I got frustrated more than once. And there was actually a point where I almost abandoned it. I thought, <em>“Maybe I should just leave this for now.”</em> But after stepping away for a while, I came back to it.</p><p>I started studying again.</p><p>I went through the concepts again and again, trying to get accustomed to them instead of expecting myself to understand everything immediately. The assignments didn’t make things easier either.</p><p>We had <strong>five courses/tasks</strong> to work through, and they covered several of the OOP concepts we were learning. So I wasn’t just reading about these concepts. I had to actually use them. And that is where things got really interesting.</p><p><strong>Works of My Hands — The Library Management System</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*bsEhdda21BOMANiGtorRvA.png" /></figure><p>One of the major tasks for this week was building an actual <strong>Library Management System</strong> using the concepts we had learnt. And when I say this was challenging…</p><p><strong>It was challenging.</strong></p><p>The system required us to bring several OOP concepts together — from classes and objects to inheritance, polymorphism, encapsulation, iterators, scope, and other features. At first, looking at the requirements felt like a lot. There were so many things to consider. How should the classes be structured? Which attributes belong where? How should the different classes relate to one another? How do I apply inheritance here? Where does polymorphism come in? How do I make the objects interact properly? It was a lot to process.</p><p>But breaking it down. <strong>One concept at a time.</strong></p><p>Instead of looking at the entire Library Management System as one huge problem, I tried to look at the individual pieces and understand what each part was supposed to do.</p><p>And slowly, it started making more sense. Not perfectly. Definitely not easily. But enough for me to keep going. Building the system also helped me realise that there is a big difference between <strong>knowing the definition of a concept and actually knowing how to use it.</strong> Putting all of them together in one working system? That was a different level of learning. And honestly, that was probably one of the biggest lessons from this week.</p><p><strong>My Laptop Had Other Plans</strong></p><p>As if the course wasn’t already challenging enough, my laptop also decided to add its own contribution to the struggle.</p><p>I’ve had some issues with my laptop this week, and trying to learn, practise, write code, make corrections, and complete assignments while dealing with those issues hasn’t exactly been fun.</p><p>But I’m managing. Somehow.</p><p><strong>What This Week Is Teaching Me</strong></p><p>Week 2 has taught me that learning something difficult requires patience. There were moments when I wanted to understand everything immediately. I wanted to look at a concept and just <em>get it.</em> But that’s not how it worked. I had to sit with the concepts. Read them. Study them. Go back to them. Look for other explanations. Make mistakes. Correct those mistakes. And try again.</p><p>I’m beginning to understand that not understanding something at first doesn’t mean I’m incapable of learning it. Sometimes, it simply means I need more time with it.</p><p>Week 1 taught me to take things one step at a time.</p><p>Week 2 reminded me why I need that mantra in the first place.</p><p>Because this week, there were definitely times when I felt like the steps were too difficult to take. But I kept taking them. And I think that’s progress too.</p><p><strong>Looking Forward</strong></p><p>As I move into the next week, I’m looking forward to becoming more comfortable with the concepts I’ve learnt so far.</p><p>I don’t want to just recognise the terms inheritance, polymorphism, encapsulation, classes, objects, and methods. I want to be able to actually use them confidently. I also want to improve my problem-solving skills because I’ve realised that understanding the syntax is only one part of the journey.</p><p>The real challenge is knowing how to approach a problem and turn what you’ve learnt into a solution.</p><p>So, here’s to another week of learning, making mistakes, asking questions, trying again, and hopefully getting a little better.</p><p>This week wasn’t easy. It wasn’t perfect. And I definitely didn’t understand everything immediately.</p><p>But I’m still here.</p><p>Still learning.</p><p>Still trying.</p><p>Still taking it…</p><p><strong>ONE STEP AT A TIME.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b74c211b4ef6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Step at a Time — My Journey to Data Science through Datara Flow]]></title>
            <link>https://medium.com/@olachiokere1995/one-step-at-a-time-my-journey-to-data-science-through-datara-flow-47f4bc23c847?source=rss-6e1dc1e76a32------2</link>
            <guid isPermaLink="false">https://medium.com/p/47f4bc23c847</guid>
            <dc:creator><![CDATA[OLACHI ROSEBUD OKERE]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 18:39:08 GMT</pubDate>
            <atom:updated>2026-09-10T18:39:08.101Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*dXjY4XmDEgDl2KZ53f5B0Q.jpeg" /></figure><p>“One step at a time.” — That has become my mantra since I commenced this 6-month data science internship programme at Datara Flow.</p><p>After deciding to upskill in my data journey, I came across the Datara Flow application link on social media. I clicked on it, applied, and voila! Before I knew it, onboarding and orientation had begun — and so had my journey.</p><h4><strong>The Beginning of Beginnings — Week 1</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DRE5eIucjvalr-O1rUL4sQ.png" /></figure><p>Fast-forward to Week 1, we were sent guidelines for installing the software that would be used throughout the internship. We were added to GitHub (and I discovered a whole new aspect of using GitHub), then came the installation and setup of VS Code, Git Bash, Tableau, Python, and Anaconda Navigator.</p><p>The team also organised a virtual technical onboarding session to take us through the setup. And honestly, it was really helpful because I was almost lost!</p><p>Then the actual learning began.</p><p>It’s been a lot. A whole lot.</p><p>There were concepts to understand, new vocabularies, new words, and so much information coming at once. We were also encouraged not to use AI, which meant I had to really sit with the concepts and figure things out for myself.</p><p>Guidelines, lessons, tasks, and assignments were issued for Week 1, featuring Python Basics.</p><p>With absolutely no knowledge of Python, I dived in immediately…</p><p>Hitting my head.</p><p>Getting a migraine.</p><p>But I dived in!</p><h4>Introduction to Data Science</h4><p>One of the things we learnt during Week 1 was an introduction to data science — what it is, what it involves, and what it means to actually work in the field.</p><p>This was particularly interesting to me because it helped me see beyond just learning how to code.</p><p>Data science is not simply about Python, writing code, or working with numbers and datasets. There is a whole process involved, from asking the right questions and collecting and cleaning data to analysing it, finding patterns, communicating insights, and using those insights to make better decisions.</p><p>But one thing stood out to me the most:</p><p><strong>The most important thing is creating impact by solving real-life problems.</strong></p><p>That really put things into perspective for me.</p><p>It made me realise that all these concepts I am learning are not just random technical skills. They are tools that can eventually be used to understand problems, find solutions, and create meaningful impact in the real world.</p><p>And that made me even more excited about the journey I had started.</p><h4><strong>Lessons Learned</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CMX8Alut3k4wQ-RmSWp9UA.png" /></figure><p>From this first week, I learnt about the different environments used in coding — VS Code, Jupyter Notebook, and Google Colab — and the basic concepts of Python.</p><p>I learnt about data types such as integers, floats, strings, lists, sets, tuples, and dictionaries. I learnt about indentation in Python, variables, loops, operators, modules, palindromes, exception and other fundamentals in python.</p><p>I also learnt how to build simple calculators, create a guessing game, create a shopping cart, and write file-handling programs.</p><p>Looking at this list now, I realise just how much I actually covered in one week.</p><p><strong>Challenges Faced</strong></p><p>Of course, it wasn’t all smooth sailing. While trying to understand these new concepts and work on my tasks and assignments, especially without the use of AI, I became overwhelmed. There seemed to be so much I didn’t know.</p><p>One of the biggest challenges for me was understanding `for` and `while` loops in Python. At some point, I didn’t even understand the problems I was trying to solve.</p><p>I would look at a task and wonder, <em>“What exactly am I supposed to do here?”</em></p><p>It was frustrating. So, What Did I Do?</p><p>I told myself… <em>“Just breathe.” </em>And then, start all over again. This time, “<em>one step at a time.”</em></p><p>I picked the first task and searched for the concept on YouTube. I watched all the videos I could find concerning the topic. I also did a lot of Google searches, and that was how I discovered a free website — W3Schools.com.</p><p>What a treasure! Kudos to the creators.</p><p>I went back to the concepts I needed to understand, and then I returned to the problem. This time, I reminded myself again:<em> </em>“take it one step at a time.”</p><p>I’d read the task like three times.</p><p>I’d try to understand the problem.</p><p>I’d list out what was required of me to solve it.</p><p>Then, I’d try to decipher the problem and figure out how to approach it.</p><p>And when I got an error message?</p><p>I started reading it.</p><p>Yes!!! I discovered that<strong> <em>reading error messages actually helps you pinpoint exactly where you went wrong.</em></strong></p><p>Instead of panicking when I saw an error, I started asking myself:</p><p>“What is this error trying to tell me?”</p><p>Then I’d make the correction and try again.</p><p>Slowly and gradually, I went through the tasks and assignments.</p><p>One task.</p><p>One concept.</p><p>One error.</p><p>One correction.</p><p>One step at a time.</p><p><strong>What This Experience Is Teaching Me?</strong></p><p>This experience is teaching me to push myself out of my comfort zone while staying resilient and focused.</p><p>I’m challenging myself to learn something completely new in a short period of time — and I’m actually doing it!</p><p>Is it easy? Absolutely not.</p><p>Have there been moments when I felt overwhelmed? Definitely.</p><p>Have I wanted to just stare at my laptop and wonder what on earth I was doing? Yes!</p><p>But I’m learning.</p><p>And perhaps more importantly, I’m learning <strong>how to learn.</strong></p><p>I’m learning that not understanding something immediately doesn’t mean I can’t understand it eventually.</p><p>Sometimes, I just need to breathe, go back, break the problem down, and take it “one step at a time.”</p><p>Because when you keep taking those little steps, you eventually look back and realise that you’ve travelled much farther than you thought.</p><p>It’s not easy, but then again…</p><p>“ONE STEP AT A TIME.”</p><p>And you wouldn’t even notice when you reach the end of the journey.</p><p>A special shoutout to the founder of Datara Flow and the entire Datara Flow team for teaching, guiding, and coaching us with so much patience.</p><p>Thank you for creating an environment where beginners like me can learn, make mistakes, ask questions, and keep trying.</p><p>This is only Week 1.</p><p>See you all in Week 2! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47f4bc23c847" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Report on Vehicle Sales Dataset-My HNG Experience]]></title>
            <link>https://medium.com/@olachiokere1995/technical-report-on-vehicle-sales-dashboard-my-hng-experience-162a83688b87?source=rss-6e1dc1e76a32------2</link>
            <guid isPermaLink="false">https://medium.com/p/162a83688b87</guid>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[OLACHI ROSEBUD OKERE]]></dc:creator>
            <pubDate>Sat, 29 Jun 2024 15:56:11 GMT</pubDate>
            <atom:updated>2024-06-29T15:58:03.177Z</atom:updated>
            <content:encoded><![CDATA[<p>This is my very first post on Medium blog and it is courtesy of <a href="http://https//hng.tech/internship">https://hng.tech/internship</a>. You can learn all about this program from the link and also follow me to keep up with this challenging experience. You can also get more information and opportunities at <a href="https://hng.tech/hire">https://hng.tech/hire</a>. Let&#39;s ride!</p><p><strong>Technical Report Summary on Vehicle Sales Dataset</strong></p><h4><strong>Introduction:</strong></h4><p>This report analyzes sales data from a vehicle company that offers various vehicle types including Classic cars, Motorcycles, Vintage Cars, Planes, Ships, Trains, Trucks, and Buses. The dataset comprises 25 columns and 2823 rows of numerical (sales sums, order quantities), categorical (status, country), and date data (order date, month ID, Year ID).</p><p><strong>Insights and Observations:</strong></p><p>The total sales over three consecutive years (2003, 2004, 2005) amounted to $10,032,328.85, peaking in 2004 at $4,724,162, followed by $3,516,979 in 2003, and $1,791,486 in 2005. Sales spiked in the last quarter (September to November) of 2003 and 2004, notably in November, but sharply declined in December both years. The top five countries by sales were USA, Spain, France, Australia, and UK, with the USA leading at 36% of total sales ($3.6 million), while Ireland had the lowest sales at approximately $57,756.</p><p>About 92% of orders were successfully shipped, indicating efficient logistics management. Medium-sized deals constituted 60% of total sales ($6 million), with small and large deals contributing $2.6 million and $1.3 million, respectively. Classic cars were the top-selling product, with sales of approximately $3.9 million and over 33,000 units sold, while trains were the least sold at around $200,000.</p><p><strong>Conclusion and Recommendations:</strong></p><p>There is a noticeable seasonal sales trend, suggesting increased marketing efforts and promotions in the last quarter to boost year-end sales. Further seasonal trend analysis is recommended to understand these patterns better, especially the declines observed in 2005.</p><p>Targeted marketing campaigns tailored to local preferences in each country, particularly the top-performing ones, should be considered for sustained growth. Understanding transportation and import systems for different countries will provide insights into sales variations. Strategies should focus on reducing orders on hold or disputed status and maintaining high shipping efficiency.</p><p>Given the preference for medium-sized deal sizes, continued focus on this category is advised. Consider incentivizing the large deal size to improve sales performance in that category.</p><p>In conclusion, further detailed analysis of sales trends, customer demographics, and market preferences will enhance decision-making. By implementing these recommendations, the company can optimize operations, enhance customer satisfaction, and drive sustainable growth in the competitive vehicle sales market.</p><p>Below is a simple chart showing observations and insights</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*Oduy1ALturWruvUT0XE7uA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=162a83688b87" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>