<?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 Yopa Nelly on Medium]]></title>
        <description><![CDATA[Stories by Yopa Nelly on Medium]]></description>
        <link>https://medium.com/@yopatatchou?source=rss-dce2159b9550------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jKpnjb6VryUTnhp-W39B6Q.jpeg</url>
            <title>Stories by Yopa Nelly on Medium</title>
            <link>https://medium.com/@yopatatchou?source=rss-dce2159b9550------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:24:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yopatatchou/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[How a Qwasar Silicon Valley scholarship took me from shell commands to Python data projects…]]></title>
            <link>https://medium.com/@yopatatchou/how-a-qwasar-silicon-valley-scholarship-took-me-from-shell-commands-to-python-data-projects-0e73245924c8?source=rss-dce2159b9550------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e73245924c8</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[tech-in-africa]]></category>
            <category><![CDATA[scholarship]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Yopa Nelly]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 12:47:28 GMT</pubDate>
            <atom:updated>2026-11-16T12:47:28.133Z</atom:updated>
            <content:encoded><![CDATA[<h3>How a Qwasar Silicon Valley scholarship took me from shell commands to Python data projects, teamwork and helping other learners</h3><p>I Completed 31 Projects and Earned My Introduction to Data Certificate: Here Is What It Taught Me</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RQ2dA_x1rQDT8sBisLNbBQ.png" /></figure><p>How a Qwasar Silicon Valley scholarship turned me from running my first shell commands to building APIs, web scrapers and data pipelines in Python</p><p>Today, November 16, 2026, I received my Introduction to Data certificate from Qwasar Silicon Valley. It recognizes the completion of 31 projects and coding exercises at Silicon Valley standards, covering the fundamentals of data with Python. I am grateful to JFN Center and PADESCE for supporting my place in this program.</p><p>A certificate is a milestone, so I want to share what is behind it.</p><p>What I built</p><p>Every project was graded by automatic tests, so a function either worked or it did not. Along the way I built:</p><p>• A Flask API that serves more than a thousand movies filtered by genre, which scored 10/10 on the automatic tests.<br>• A web scraper using requests and BeautifulSoup that collects the top 25 trending GitHub repositories and formats them as a CSV.<br>• A data pipeline that cleans raw sales records, groups them by email provider, age and time of day, and counts the values per column as JSON.<br>• My own version of printf in C, built with system calls and variadic arguments, and a recreation of the cat command.<br>• Many smaller functions on strings, arrays, recursion and file handling, including a Levenshtein distance and a Roman numeral converter.</p><p>What the tests taught me</p><p>Automatic tests do not forgive small mistakes, and that made me a more careful engineer. I learned to:</p><p>1. Read an error message first, because it usually says exactly what is wrong.<br>2. Debug one problem at a time, from a function returning None to a JSON response with the wrong content type.<br>3. Write a clear README for every project, because explaining my work shows what I really understood.<br>4. Commit small and often, with a clear message for each step.</p><p>Working in a team</p><p>My First Scraper was a team project, and I did it with a fellow learner. We split the work: I wrote the request and transform functions, and my teammate wrote the extraction and formatting. We shared a Git repository, so we had to pull before we pushed, resolve a merge conflict, and test the whole chain together. When a typo in one function broke the pipeline, we found it, fixed it, and passed 4 out of 4 tests. Good teamwork is mostly clear communication, and I now have a real example of it.</p><p>Helping others along the way</p><p>I learned that I understand something best when I explain it. Some of my fellow learners are still struggling with the tasks, and some find the English in the instructions a barrier. So I have been sharing what I understand, helping people get unstuck, and proposing peer learning sessions where we learn together and help each other. As someone who co-organizes tech communities in my region, I believe that nobody should be left behind in tech because of language or access.</p><p>What I bring</p><p>• Python for data work: scraping, cleaning, transforming and serving data<br>• Git and GitHub collaboration, including conflicts and code reviews<br>• Debugging from error messages and test reports<br>• Clear documentation and a habit of testing before submitting<br>• Patience in explaining technical ideas to people at different levels</p><p>What is next</p><p>I am continuing with C, pointers and memory management, and I am looking forward to more advanced data and DevOps projects. I would love to hear from teams and mentors working in data, Python or DevOps.</p><p>You can connect with me on LinkedIn (linkedin.com/in/yopa-nelly) and follow my work on GitHub (github.com/YopaNelly).</p><p>Thank you to JFN Center, PADESCE and Qwasar Silicon Valley, and to my teammate and every learner who has shared this road with me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e73245924c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Got a Scholarship to Learn DevOps. Here Is What I Have Built So Far]]></title>
            <link>https://medium.com/@yopatatchou/i-got-a-scholarship-to-learn-devops-here-is-what-i-have-built-so-far-80f17fcdc151?source=rss-dce2159b9550------2</link>
            <guid isPermaLink="false">https://medium.com/p/80f17fcdc151</guid>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[women]]></category>
            <category><![CDATA[scholarship]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Yopa Nelly]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 12:39:35 GMT</pubDate>
            <atom:updated>2026-11-13T12:39:35.075Z</atom:updated>
            <content:encoded><![CDATA[<p>From Zero to Shell, Python and APIs: My First Weeks as a Qwasar Silicon Valley Scholar</p><p>What I have built and learned since joining a scholarship program supported by JFN Center and PADESCE</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Ka4eOcvuW_dELGLWzO7-bQ.jpeg" /></figure><p>I recently joined a scholarship program supported by JFN Center and PADESCE, with training delivered by Qwasar Silicon Valley. The program gives learners in Cameroon hands-on training in software engineering and DevOps, with real projects, automatic tests and peer reviews. This post is about what I have built and learned so far.</p><p>Starting with the shell</p><p>I began in the terminal with commands like touch, ls, chmod and cat. I learned that file permissions such as r — r-xr-x are just numbers added together: read is 4, write is 2 and execute is 1. That makes the permission above 455.</p><p>Git came next. I learned to commit each exercise separately with a clear message and to push my work often.</p><p>Python, one small function at a time</p><p>From there I moved through Python quests on variables, loops, functions, strings and arrays. Some exercises taught me to read my own mistakes:</p><p>• My function returned None, which meant it never reached a return statement.<br>• Test calls left in my file added extra output and made the checker fail.<br>• A NameError showed me that the function name must match the subject exactly.</p><p>Projects I am proud of</p><p>• my_printf in C: my own version of printf, built with write and variadic arguments.<br>• my_cat: a recreation of the cat command.<br>• my_levenshtein and a Roman numerals converter: string comparison and number conversion.<br>• A CSV parser and data pipeline: turning raw sales data into groups and counting values per column as JSON.<br>• My IMDB API: a Flask backend that serves more than a thousand movies, filtered by genre.</p><p>The IMDB API taught me the most. The tests failed twice before they passed. The first time, my JSON content type was not what the tests expected. The second time, my data file was missing from the repository. After fixing both, I scored 10/10.</p><p>What I learned about learning</p><p>1. Read the error message first, because it usually says exactly what is wrong.<br>2. Commit small and often.<br>3. Write a README for every project, because explaining it shows what you really understood.<br>4. Daily stand-up reports keep you honest about your progress and your blockers.</p><p>What is next</p><p>I will keep building through the program, with more Python quests, DevOps tools and team projects. I also have a web scraping project that I will complete with a teammate, and I will write about it when it is done. As someone who organizes tech communities in Bamenda, I want to share what I learn with other young people and women in tech in my region, so that more of us can find opportunities like this one.</p><p>Thank you to JFN Center, PADESCE and Qwasar Silicon Valley for this opportunity, and to my fellow learners and mentors who help me along the way.</p><p>You can follow my work on GitHub: github.com/YopaNelly/qwasar-devops-journey</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80f17fcdc151" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Paper to Database: What I Learned Curating a Microbiome Study for BugSigDB]]></title>
            <link>https://medium.com/@yopatatchou/from-paper-to-database-what-i-learned-curating-a-microbiome-study-for-bugsigdb-4b428a459ac0?source=rss-dce2159b9550------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b428a459ac0</guid>
            <category><![CDATA[microbiome]]></category>
            <category><![CDATA[bioinformatics]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Yopa Nelly]]></dc:creator>
            <pubDate>Fri, 06 Nov 2026 15:39:44 GMT</pubDate>
            <atom:updated>2026-11-06T15:39:44.645Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A beginner-friendly guide, with the tricky words explained</em></p><p>By Yopa Nelly</p><p>Imagine reading a science paper and turning every important finding into neat rows of data that other scientists, and computers, can search. That is what a BugSigDB curator does. This time I curated a study about baby mice, a virus, and a natural compound found in pomegranate peel.</p><p>In this post I’ll share how it went, what tripped me up, and what I would tell anyone starting out. Whenever a big word shows up, I’ll break it down.</p><h3>What is BugSigDB, in plain words?</h3><p>Your gut is home to trillions of tiny living things, mostly bacteria. Together they are called the <strong>microbiome</strong>. Scientists often compare the microbiomes of two groups, such as sick vs. healthy or treated vs. untreated, and report which bacteria are more or less common in one group.</p><p><strong>BugSigDB</strong> collects those findings in one place so people can compare studies side by side. A curator reads a paper and enters its findings by following a shared rulebook called the curation policy.</p><p>The key word here is <strong>microbial signature</strong>. Think of a party guest list: it tells you which bacteria showed up <em>more</em> (increased) or <em>less</em> (decreased) in one group compared with another. One list of bacteria is one signature.</p><h3>The study I curated</h3><p>The paper tested whether a natural compound called <strong>ellagic acid</strong> (found in pomegranate peel) could help baby mice recover from <strong>rotavirus</strong>, a virus that causes tummy infections and diarrhea, mostly in young children. The researchers infected the mice, gave some of them ellagic acid at three doses (low, medium and high), and then looked at the bacteria in their guts.</p><p>The paper is Zheng et al., 2025, in <em>Frontiers in Cellular and Infection Microbiology</em> (PMID 41532082). You can see my curation here: <a href="https://bugsigdb.org/41532082">https://bugsigdb.org/41532082</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/924/1*Ja32v7OAUhwEnpbBhBWgjg.png" /></figure><p>In BugSigDB, one <strong>experiment</strong> means one comparison between two groups. My study ended up with six:</p><ul><li>Infected mice vs. uninfected mice</li><li>Low-dose ellagic acid vs. infected mice with no treatment</li><li>Medium-dose vs. infected mice with no treatment</li><li>High-dose vs. infected mice with no treatment</li><li>Two more comparisons from a different counting method (qPCR, explained below)</li></ul><p>That gave me 10 signatures and more than 100 bacteria entries. It sounds like a lot, but it is just careful, patient reading.</p><h3>The jargon decoder</h3><p>Here are the words that confused me at first, in everyday language.</p><ul><li><strong>16S (V3 to V4):</strong> Every bacterium carries a gene that works like a barcode, and reading it tells you who is who. The barcode has sections numbered V1 to V9. This paper read the middle stretch, V3 to V4.</li><li><strong>Taxon / taxa:</strong> A taxon is a name on the bacteria family tree, like an address that can be as broad as a country (phylum) or as exact as a street (species). Curators enter each bacterium at the level the paper reports.</li><li><strong>NCBI Taxonomy ID:</strong> An ID number for each bacterium, like an ID card. Names change over time, but the ID stays the same, so everyone is talking about the same bacterium.</li><li><strong>LEfSe and LDA score:</strong> LEfSe is a spot-the-difference tool that finds the bacteria that best tell two groups apart. The LDA score is how loud that difference is. This paper only counted differences above a score of 2.</li><li><strong>Multiple testing correction:</strong> If you test hundreds of bacteria, a few will look special just by luck, like flipping lots of coins. A correction is a stricter bouncer at the door. This paper didn’t mention one, so I entered No.</li><li><strong>qPCR:</strong> Instead of listening to the whole crowd, you ask, how much of <em>this one</em> bacterium is here? The paper used it to count three specific Lactobacillus bacteria.</li><li><strong>Alpha diversity:</strong> How varied the community is, or how many different kinds of guests came to the party. If the paper reports no real difference, you enter unchanged.</li><li><strong>Group 0 and Group 1:</strong> Group 0 is the comparison group (the control). Group 1 is the group that got the exposure or treatment. Every signature is written from Group 1’s point of view.</li><li><strong>EFO (the condition):</strong> A dictionary of standard names for health conditions and treatments, so everyone uses the same words.</li></ul><h3>What I’d tell a new curator</h3><p><strong>1. Read the policy first, then annotate the PDF.</strong> Highlight where each field comes from (sequencing type, groups, tests) and add a short note. It saves you from hunting through the paper later.</p><p><strong>2. Zoom into the figures, and check the legend colors.</strong> In these plots, the color of a bar tells you which group a bacterium is more common in. A bar in the Group 1 color is <em>increased</em> in Group 1. Then check your reading against the paper’s text. If they disagree, look again before changing anything.</p><p><strong>3. Hunt for every comparison.</strong> I almost missed a figure with the qPCR results. A second pair of eyes caught it. Scan every figure and table for group-vs-group results.</p><p><strong>4. Use the paper’s group names and spell out abbreviations.</strong> Put the details in the group definition, such as doses, timing and how many animals per group.</p><p><strong>5. Expect messy bacteria names.</strong> Use the autocomplete first. A name that stays orange didn’t match NCBI. NCBI also renames things over time, so the wiki may show a newer name for the bacterium you typed. If you check the NCBI page and your name is listed as a synonym, you’re fine. If a name truly doesn’t exist in NCBI, enter it exactly as the paper writes it.</p><p><strong>6. Pick the closest condition, and ask when unsure.</strong> My study tested a drug, but the exact term wasn’t in the list. I asked, got several opinions, and ended up with a closest-fit term.</p><p><strong>7. Blank is better than a guess.</strong> If the paper doesn’t report a result for a comparison (like diversity), leave it blank instead of inventing something.</p><p><strong>8. Be patient when saving.</strong> Saving can be slow, and clicking again can create duplicates. Wait, refresh, and if something does get duplicated, ask for it to be deleted and give the exact page link.</p><p><strong>9. Ask for peer review early.</strong> My curation got much better after review: clearer group names, better definitions, fixed taxa, and extra experiments. When a comment surprised me, I double-checked it against the figure and replied politely. Reviewers don’t always agree, and that is okay. The project’s reviewers make the final call.</p><p><strong>10. Be honest about your tools.</strong> I used an AI assistant to help me double-check things and read tiny figure labels. I entered everything myself and checked it against the paper. Saying so builds trust.</p><h3>Why I keep coming back</h3><p>Curation feels like detective work with a purpose. Each study you enter becomes a piece of a bigger puzzle that other researchers can use. And you learn something new with every study, whether it is a bacteria name, a statistics term, or a better way to read a figure.</p><p>If you’re curious, look at BugSigDB (https://bugsigdb.org). Start small, read the policy, and don’t be shy about asking questions. The community is generous.</p><p>Thanks for reading! If this helped you, share it with someone starting their first curation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b428a459ac0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ They Spent 20 Years Warning Me About Boys. Now They Want a Husband by Friday.]]></title>
            <link>https://medium.com/@yopatatchou/they-spent-20-years-warning-me-about-boys-now-they-want-a-husband-by-friday-54a1e661aad1?source=rss-dce2159b9550------2</link>
            <guid isPermaLink="false">https://medium.com/p/54a1e661aad1</guid>
            <category><![CDATA[women]]></category>
            <category><![CDATA[personal-essay]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[relationships]]></category>
            <category><![CDATA[marriage]]></category>
            <dc:creator><![CDATA[Yopa Nelly]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 16:34:59 GMT</pubDate>
            <atom:updated>2026-10-08T16:37:10.761Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>So… When Exactly Was I Supposed to Get a Boyfriend?</strong></p><p>At 13, my mother sat me down like she was announcing a national emergency.</p><p>“From now on, be careful with boys.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*J4Tm5MxtqUbJzGeh3Qyiag.png" /></figure><p>Wonderful. Message received. Here is my lifetime manual:</p><p><em>If a boy calls you, don’t go.</em><br> <em>Don’t follow boys anywhere.</em><br> <em>Don’t joke with boys.</em><br> <em>Remember you are a child of God.</em><br> <em>Focus on your studies.</em></p><p><strong>Boys = danger. Books = salvation.</strong> Very clear. Very consistent. Very <em>no room for interpretation.</em></p><p>Primary school: same message.<br> Secondary school: same message, now with a microphone.<br> University: “You’re living alone now. It’s a DANGER ZONE.”</p><p><strong>Year 1:</strong> Focus.<br> <strong>Year 2:</strong> Focus.<br> <strong>Year 3:</strong> Don’t let anybody distract you.<br> <strong>Year 4:</strong> CONCENTRATE!</p><p>And me? I obeyed like a soldier. I concentrated so hard I should have graduated with a medal for Outstanding Avoidance of Men.</p><p>Then I finished my Bachelor’s degree. And someone leaned in, smiling like nothing had ever happened:</p><p><strong>“So… don’t you have a boyfriend?”</strong></p><p>Oh. <em>Oh.</em> So the villain I was trained to flee for twenty years is now a <strong>requirement</strong>? Interesting. Did the policy change? Was there a memo? Because I must have missed the email.</p><p>I said I was going for my Master’s. They nodded: “Very good. But… don’t you have a guy who wants to marry you?”</p><p>Of course. Because nothing says “congratulations on your education” like asking about a man who doesn’t exist. Let me show you my timetable, since apparently I’ve been negligent:</p><p><strong>Monday:</strong> Classes<br> <strong>Tuesday:</strong> Assignments<br> <strong>Wednesday:</strong> Study<br> <strong>Thursday:</strong> Projects<br> <strong>Friday:</strong> Group work<br> <strong>Saturday:</strong> Laundry<br> <strong>Sunday:</strong> Church + preparing for Monday</p><p>Please point out where “locate husband” fits. Between laundry and Jesus? I’ll wait.</p><p>Then an aunty looks me in the eye and says, “Nowadays men fear intelligent women.”</p><p>Ma. <strong>YOU told me to become intelligent.</strong> You can’t build the product and then complain that the market doesn’t want it.</p><p>I did everything right. I was obedient, focused, prayerful, and academically excellent. And my reward is being asked to produce a fiancé like it’s a group assignment due Friday.</p><p>In fairness, I know it all came from love. They wanted to protect me, and I’m grateful. But somewhere between “run from boys” and “where is your husband,” someone forgot to write the chapter in the middle.</p><p>So if you see me walking around peacefully, please don’t ask where my boyfriend is. <strong>I’m still recovering from the instructions.</strong></p><p>Anyway, I’m exploring.</p><p>And honestly? <strong>I see there are nice men out here.</strong></p><p>African girls, tell me: did your parents also spend 20 years building the fortress, then ask why nobody got in? <strong>We need to talk.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a1e661aad1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Thought Michelle Obama Had Nothing to Teach Me. I Was Wrong.]]></title>
            <link>https://medium.com/@yopatatchou/i-thought-michelle-obama-had-nothing-to-teach-me-i-was-wrong-455c86e14926?source=rss-dce2159b9550------2</link>
            <guid isPermaLink="false">https://medium.com/p/455c86e14926</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[women]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Yopa Nelly]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 15:44:06 GMT</pubDate>
            <atom:updated>2026-10-07T15:44:06.317Z</atom:updated>
            <content:encoded><![CDATA[<p>How one book challenged my assumptions about success, fear, and figuring life out.</p><h3>I thought I knew exactly what Michelle Obama was going to teach me.</h3><p>I was wrong.</p><p>When I first saw <em>The Light We Carry</em>, I looked at the cover and honestly wondered, <em>“What can this woman possibly teach me?”</em></p><p>I had never met her. I had never lived her life. And yet, in less than a minute, I had already decided what her book was going to be about.</p><p>That was my first mistake.</p><p>The second was almost not reading it.</p><p>And the funny thing is, I didn’t even choose the book.</p><p><strong>My brother did.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AcQXC-klxmKoHX2MXXP3LA.png" /></figure><h3>It started with a visit to my brother’s house</h3><p>One day, I went to visit my elder brother.</p><p>And as the little sister, I believe there are certain rights that come with entering your elder brother’s house.</p><p>One of them is inspecting his books. 😂</p><p>So naturally, I started looking through his bookshelf.</p><p>Then I saw it.</p><p><em>Things Fall Apart</em>.</p><p>I had been wanting to read it for a while, so I asked him if I could take it.</p><p>He told me he wasn’t finished with it yet.</p><p>Of course.</p><p>So I asked him to give me another book.</p><p>He looked through his collection and handed me <em>The Light We Carry</em> by Michelle Obama.</p><p>I looked at the cover.</p><p>Then I looked at him.</p><p>And somewhere in my mind I was still thinking:</p><p><em>Michelle Obama? Really?</em></p><p>But I took the book anyway.</p><p>At the time, I didn’t know that my brother had just given me a book I would think about long after I finished reading it.</p><h3>Then came the Bambili electricity problem</h3><p>I took the books back with me to Bambili.</p><p>If you know Bambili, you already understand where this is going. 😂</p><p>The electricity situation was doing what it does best.</p><p>Sometimes there was light.</p><p>Sometimes there wasn’t.</p><p>And sometimes you could spend enough time waiting for electricity to return that you started questioning all your life decisions.</p><p>So one day, with nothing much to do, I finally picked up Michelle Obama’s book.</p><p>I started reading.</p><p>And then something unexpected happened.</p><p><strong>I became interested.</strong></p><p>Very interested.</p><p>The woman I had mentally dismissed before opening the book was suddenly telling me things that felt surprisingly familiar.</p><p>Not because I had lived her life.</p><p>I obviously hadn’t.</p><p>But because underneath the title of “former First Lady of the United States” was simply a human being trying to figure things out.</p><p>She talked about uncertainty.</p><p>Fear.</p><p>Relationships.</p><p>Family.</p><p>Pressure.</p><p>Finding your voice.</p><p>Growing into different versions of yourself.</p><p>And the strange reality that even after achieving things you once dreamed about, you can still find yourself wondering:</p><p><em>Am I doing this right?</em></p><p>That part stayed with me.</p><p>Because sometimes we imagine successful people as if they have reached a point where life becomes clear.</p><p>As if getting the degree, the job, the money, the title, or the position automatically removes doubt.</p><p>But Michelle Obama’s story reminded me that it doesn’t work that way.</p><p>You can be extremely successful and still be figuring things out.</p><p>You can be admired by millions of people and still have moments when you question yourself.</p><p>You can become a First Lady and still have to learn how to carry fear, expectations, relationships, responsibilities, and your own identity.</p><p>And maybe that is one of the most important things I took from the book.</p><h3>Success doesn’t mean you stop being human</h3><p>I think we sometimes put successful people on another level.</p><p>We see the achievements but not the uncertainty that came before them.</p><p>We see the finished product but not the years of becoming.</p><p>We see someone standing confidently on a stage and forget that they probably had moments when they didn’t feel confident at all.</p><p>Reading <em>The Light We Carry</em> made me think about my own life differently.</p><p>Especially as a young woman trying to build a career in technology.</p><p>Sometimes I look at people who are already doing amazing things and wonder if I’m behind.</p><p>Someone is already working.</p><p>Someone is building a company.</p><p>Someone is doing AI research.</p><p>Someone is travelling.</p><p>Someone seems to know exactly what they want.</p><p>And I’m here thinking:</p><p><em>Okay… so what am I actually doing with my life?</em> 😭</p><p>But maybe figuring things out is not evidence that you’re failing.</p><p>Maybe it is simply part of becoming.</p><h3>The lesson I wasn’t expecting</h3><p>One of the ideas I carried with me from the book is that we don’t always need to have everything figured out.</p><p>Sometimes, we just need enough clarity to take the next step.</p><p>That reminded me of something very simple.</p><p><strong>You don’t always need enough light to see the entire road. Sometimes, you only need enough light to see the next step.</strong></p><p>And maybe that is where I had misunderstood the whole point of the book.</p><p>I thought Michelle Obama was going to give me answers.</p><p>Instead, she gave me better questions.</p><p>How one book challenged my assumptions about success, fear, and figuring life out.Questions about who I am.</p><p>What I believe.</p><p>What I am afraid of.</p><p>What I am carrying.</p><p>What I want to become.</p><p>And whether the person I am becoming is actually someone I want to be.</p><h3>We judge things before we know their story</h3><p>Looking back, what surprises me most isn’t even how much I learned from the book.</p><p>It is how quickly I had judged it.</p><p>I had barely opened it.</p><p>I had already decided what it was going to be about.</p><p>And isn’t that something we all do?</p><p>We meet someone and create a story about them before they speak.</p><p>We see someone’s success and assume their life must be easy.</p><p>We see a book and decide whether it is worth reading from the cover.</p><p>We hear one thing about someone and think we already understand the whole person.</p><p>Sometimes, we are wrong.</p><p>Very wrong.</p><p>And sometimes, we only discover that after giving ourselves enough time to actually listen.</p><h3>And yes, I still want Things Fall Apart</h3><p>The funny thing is, I still want to read <em>Things Fall Apart</em>. 😂</p><p>But now I’m actually grateful my brother wasn’t finished with it that day.</p><p>Because if he had been, I might have picked up the book I wanted and completely missed the book I needed.</p><p>I went to my brother’s house looking for a story by Chinua Achebe.</p><p>I came back with Michelle Obama’s story.</p><p>And somewhere between the electricity cuts in Bambili, the pages of that book, and my own assumptions, I learned something I wasn’t expecting:</p><p><strong>Sometimes the stories we almost ignore are the ones that have something to teach us.</strong></p><p>Maybe we just need to be humble enough to open the book.</p><p>To listen.</p><p>To read.</p><p>To ask questions.</p><p>And to admit when our first impression was wrong.</p><p>Because sometimes, a book doesn’t change your life by giving you a completely new life.</p><p>Sometimes, it simply changes the way you look at the life you already have.</p><p>And maybe that’s what good stories are supposed to do.</p><p><strong>They don’t always give us answers.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/712/1*ZONOSh7mSwcEv3ba7EdUcQ.png" /></figure><p><strong>Sometimes, they simply make us ask better questions.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=455c86e14926" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>