<?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 Rahma Nasir Iro on Medium]]></title>
        <description><![CDATA[Stories by Rahma Nasir Iro on Medium]]></description>
        <link>https://medium.com/@irorahmah?source=rss-2de09eb7e695------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rs0V2v8Ky1n2UlFODaYLNQ.png</url>
            <title>Stories by Rahma Nasir Iro on Medium</title>
            <link>https://medium.com/@irorahmah?source=rss-2de09eb7e695------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:30:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@irorahmah/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[Day 16 of 100 Days of Python: Intermediate Object-Oriented Programming (OOP)]]></title>
            <link>https://medium.com/@irorahmah/day-16-of-100-days-of-python-intermediate-object-oriented-programming-oop-f421e50eb318?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/f421e50eb318</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Sun, 28 Dec 2025 18:17:42 GMT</pubDate>
            <atom:updated>2025-12-28T18:17:42.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*UstPRSb3sbXFc6YHk6Az_w.png" /></figure><p>Today, I dived into <strong>Day 16</strong> of Angela Yu’s <em>100 Days of Python</em> course, which focuses on <strong>Intermediate Object-Oriented Programming (OOP)</strong>. This day marked a significant transition from procedural programming to structuring code using <strong>classes and objects</strong>, a fundamental concept in Python and software development.</p><h3>Why We Need Object-Oriented Programming (OOP)</h3><p>As I progressed through the first 15 days, I realized that while procedural programming works, it can get <strong>messy and hard to maintain</strong> for complex projects. For example, my Day 15 project, the <strong>Coffee Machine</strong>, relied on global variables and independent functions. While functional, it wasn’t modular — all the logic was scattered.</p><p>OOP solves this by organizing code into <strong>blueprints (classes)</strong> and <strong>instances (objects)</strong>, allowing for:</p><ul><li><strong>Encapsulation</strong> — grouping data (attributes) and behavior (methods) together.</li><li><strong>Modularity</strong> — each class handles a specific responsibility.</li><li><strong>Reusability</strong> — create multiple objects from the same class without rewriting code.</li><li><strong>Readability and maintainability</strong> — code is easier to understand and extend.</li></ul><h3>Understanding Classes and Objects</h3><h3>Class</h3><p>A class is like a blueprint for a real-world entity. It defines:</p><ul><li><strong>Attributes</strong> — what the object has</li><li><strong>Methods</strong> — what the object can do</li></ul><p>For example, in a restaurant scenario:</p><pre>Class: Waiter<br>Attributes: name, tables_assigned<br>Methods: take_order(), serve_food()</pre><h3>Object</h3><p>An object is an <strong>instance of a class</strong>, representing an actual entity based on that blueprint.</p><pre>waiter1 = Waiter(&quot;Ali&quot;, 3)<br>waiter2 = Waiter(&quot;Zainab&quot;, 5)</pre><p>Here, waiter1 and waiter2 are objects with their own attributes and behaviors.</p><h3>Accessing Attributes and Methods</h3><p>Objects interact using <strong>dot notation</strong>:</p><pre>print(waiter1.name)   # Accessing attribute<br>waiter1.take_order()  # Calling method</pre><p>Inside the class, self refers to the <strong>current object</strong>, allowing methods to access and modify its attributes.</p><h3>Adding Python Packages Using PyPI</h3><p>Day 16 also introduced working with <strong>Python packages</strong> via PyPI:</p><ul><li><strong>PyPI (Python Package Index)</strong> is like a giant library of Python tools.</li><li>Packages can be installed using <strong>pip</strong>:</li></ul><pre>pip install prettytable</pre><ul><li>Once installed, you can <strong>import and use classes and methods</strong> from these packages, just like built-in Python modules.</li></ul><p>For example, prettytable allows you to display data in clean tables, and under the hood, it uses <strong>object-oriented programming</strong>.</p><h3>Practice: Modifying Object Attributes and Calling Methods</h3><p>Before the main project, we practiced:</p><ol><li>Creating a simple class</li><li>Adding attributes</li><li>Writing methods</li><li>Modifying attributes dynamically</li><li>Calling methods on objects</li></ol><p>This helped solidify the core concepts of <strong>constructing objects, accessing attributes, and calling methods</strong>.</p><h3>Project: Coffee Machine in OOP</h3><p>The highlight of Day 16 was <strong>rebuilding the Coffee Machine</strong> from Day 15, but this time using <strong>object-oriented programming</strong>.</p><h4>Classes Used</h4><p><strong>MenuItem</strong> — represents a drink</p><ul><li>Attributes: name, cost, ingredients</li></ul><p><strong>Menu</strong> — represents the collection of available drinks</p><ul><li>Methods:</li><li>get_items() → returns all drink names</li><li>find_drink(order_name) → returns the MenuItem object</li></ul><p><strong>CoffeeMaker</strong> — handles resources and coffee preparation</p><ul><li>Methods:</li><li>report() → prints remaining ingredients</li><li>is_resource_sufficient(drink) → checks if enough ingredients are available</li><li>make_coffee(order) → deducts ingredients and confirms the order</li></ul><p><strong>MoneyMachine</strong> — handles payment processing</p><ul><li>Methods:</li><li>report() → prints current profit</li><li>make_payment(cost) → processes payment and returns True/False</li></ul><h4>Program Flow</h4><p><strong>Initialize objects</strong></p><pre>money_machine = MoneyMachine()<br>coffee_maker = CoffeeMaker()<br>menu = Menu()</pre><p><strong>Start main loop</strong></p><pre>is_on = True<br>while is_on:<br>    options = menu.get_items()<br>    choice = input(f&quot;What would you like ({options})? &quot;)</pre><p><strong>Handle commands</strong></p><ul><li>&quot;off&quot; → stops the machine</li><li>&quot;report&quot; → prints resource and money reports</li></ul><p><strong>Process drink order</strong></p><pre>drink = menu.find_drink(choice)<br>if coffee_maker.is_resource_sufficient(drink) and money_machine.make_payment(drink.cost):<br>    coffee_maker.make_coffee(drink)pyth</pre><ul><li>Checks ingredients and payment</li><li>Deducts ingredients and confirms the coffee</li></ul><h3>Key Takeaways from Day 16</h3><ol><li><strong>OOP organizes code into modular, reusable blocks</strong></li><li><strong>Attributes store data; methods perform actions</strong></li><li><strong>Objects are instances of classes</strong></li><li><strong>Dot notation</strong> is used to access attributes and call methods</li><li><strong>PyPI packages</strong> can be installed and used in an object-oriented way</li><li>Rewriting the <strong>Coffee Machine</strong> in OOP made the code <strong>cleaner, more modular, and easier to extend</strong></li></ol><h3>Conclusion</h3><p>Day 16 was a pivotal point in my Python journey. By transitioning from procedural programming to <strong>object-oriented programming</strong>, I gained a deeper understanding of <strong>how to structure code for real-world applications</strong>.</p><p>The OOP Coffee Machine project demonstrated the power of classes and objects, showing how <strong>encapsulation, modularity, and reusability</strong> make Python programs more professional and maintainable.</p><p>Next, I am excited to <strong>practice OOP further</strong> by exploring more complex projects and combining it with external Python packages.</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f421e50eb318" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[☕ Day 15 of 100 Days of Python: Intermediate, Local Development Environment Setup, and the Coffee…]]></title>
            <link>https://medium.com/@irorahmah/day-15-of-100-days-of-python-intermediate-local-development-environment-setup-and-the-coffee-456094a018fb?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/456094a018fb</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coffee]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Wed, 24 Dec 2025 18:00:04 GMT</pubDate>
            <atom:updated>2025-12-24T18:00:04.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*0oYZva3UOhDvIV2gUm2-Ig.png" /></figure><h3>☕ Day 15 of 100 Days of Python: Intermediate, Local Development Environment Setup, and the Coffee Machine:</h3><p>Learning programming is not just about syntax — it’s about learning <strong>how to think</strong>, <strong>how to model real-world problems</strong>, and <strong>how to break complexity into manageable logic</strong>.<br> Day 15 of the <em>100 Days of Python</em> challenge was a major turning point for me because it introduced all of these ideas through a surprisingly simple but powerful project: <strong>a Coffee Machine simulation</strong>.</p><p>In this article, I’ll walk you through:</p><ul><li>What the project does</li><li>How it works internally</li><li>The key programming concepts I practiced</li><li>What I learned as a beginner Python developer</li></ul><h3>🧠 Project Overview</h3><p>The goal was to create a <strong>command-line coffee machine</strong> that behaves like a real one.</p><p>The program allows users to:</p><ul><li>Order drinks (espresso, latte, cappuccino)</li><li>Pay using coins</li><li>Receive change if they overpay</li><li>Get refunded if payment is insufficient</li><li>Track available resources (water, milk, coffee)</li><li>Track total profit</li><li>Shut down or display a report when needed</li></ul><p>All of this is handled through <strong>Python logic only — no external libraries</strong>.</p><h3>☕ Available Drinks</h3><p>Each drink has:</p><ul><li>Required ingredients</li><li>A fixed cost</li></ul><p>These values are stored in a nested Python dictionary, which made it easy to scale and access.</p><h3>🧩 How the Program Works</h3><h4>1️⃣ User Input Loop</h4><p>The program runs continuously using a while loop and asks:</p><pre>What would you like? (espresso/latte/cappuccino):</pre><p>The loop only stops if the user enters:</p><pre>off</pre><h4>2️⃣ Resource Management</h4><p>Before making a drink, the machine checks whether enough ingredients are available.</p><p>If resources are insufficient, the program immediately stops the process and notifies the user:</p><pre>Sorry there is not enough water.</pre><p>This taught me how to <strong>validate conditions early</strong> to prevent logical errors.</p><h4>3️⃣ Coin Processing</h4><p>The user inserts coins in four denominations:</p><ul><li>Quarters</li><li>Dimes</li><li>Nickels</li><li>Pennies</li></ul><p>The program calculates the total amount entered and returns it as a float.</p><p>This step helped reinforce:</p><ul><li>User input handling</li><li>Arithmetic operations</li><li>Floating-point precision</li></ul><h3>4️⃣ Transaction Validation</h3><p>Once payment is received:</p><ul><li>If the money is <strong>less than the drink cost</strong>, the transaction fails and money is refunded</li><li>If the money is <strong>equal or greater</strong>, the transaction succeeds</li><li>Any extra amount is returned as <strong>change (rounded to 2 decimal places)</strong></li></ul><p>This logic closely mirrors real-world payment systems.</p><h4>5️⃣ Making the Coffee ☕</h4><p>If everything checks out:</p><ul><li>Ingredients are deducted from available resources</li><li>Profit is increased</li><li>The user receives confirmation</li></ul><p>Example:</p><pre>Here is your latte ☕️. Enjoy!</pre><h4>🛠 Key Programming Concepts Practiced</h4><p>This project helped me practice and understand:</p><ul><li>Dictionaries (including nested dictionaries)</li><li>Functions and modular programming</li><li>Global vs local scope</li><li>Conditional statements</li><li>Loops</li><li>Input validation</li><li>Resource tracking</li><li>Problem decomposition</li></ul><p>More importantly, it taught me <strong>how to think like a programmer</strong>, not just how to write Python code.</p><h4>🚀 What I Learned</h4><p>This project made me realize:</p><ul><li>Clean logic matters more than clever tricks</li><li>Breaking problems into functions makes code readable and maintainable</li><li>Even simple programs can model complex real-world systems</li><li>Confidence grows when you finish a project end-to-end</li></ul><h4>📌 Final Thoughts</h4><p>The Coffee Machine project might look simple on the surface, but it packs a lot of foundational programming lessons.<br> It strengthened my understanding of <strong>logic flow, functions, and state management</strong>, which are essential for backend development and real applications.</p><p>On to the next day ☕🐍</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=456094a018fb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Today in my 100 Days of Python journey, I tackled Day 14 and built an interactive game: Higher or…]]></title>
            <link>https://medium.com/@irorahmah/today-in-my-100-days-of-python-journey-i-tackled-day-14-and-built-an-interactive-game-higher-or-f312f8aba692?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/f312f8aba692</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 15:11:17 GMT</pubDate>
            <atom:updated>2025-12-23T15:11:17.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*b7BA9G5MhEpLsft4kwbf4w.png" /></figure><p>Today in my <strong>100 Days of Python journey</strong>, I tackled <strong>Day 14</strong> and built an interactive game: <strong>Higher or Lower</strong>. It’s a fun, simple game that tests your intuition and knowledge about social media (Instagram) popularity.</p><h3>🎮 What is the Higher or Lower Game?</h3><p>The idea is straightforward:</p><ul><li>Two accounts are displayed, each with some information: <strong>name, description, and country</strong>.</li><li>You guess which account has <strong>more followers on Instagram</strong>.</li><li>If your guess is correct, your <strong>score increases by 1</strong>, and the next round begins.</li><li>If your guess is wrong, the game ends, and your <strong>final score</strong> is displayed.</li></ul><p>For example:</p><pre>Compare A: Kendrick Lamar, a Musician, from USA<br>VS<br>Against B: Selena Gomez, a Musician, from USA<br>Who has more followers? Type &#39;A&#39; or &#39;B&#39;: b</pre><p>If you guessed right, you move to the next comparison. If not, game over.</p><h4>🛠 How I Built It</h4><p>Here’s how I structured the game:</p><h4>1. Using Functions</h4><p>I created functions to make the code clean and reusable:</p><pre>def format_data(account):<br>    &quot;&quot;&quot;Return account info as a formatted string.&quot;&quot;&quot;<br>    return f&quot;{account[&#39;name&#39;]}, a {account[&#39;description&#39;]}, from {account[&#39;country&#39;]}&quot;<br>def check_answer(user_guess, a_followers, b_followers):<br>    &quot;&quot;&quot;Check if the player&#39;s guess is correct.&quot;&quot;&quot;<br>    if a_followers &gt; b_followers:<br>        return user_guess == &quot;a&quot;<br>    else:<br>        return user_guess == &quot;b&quot;</pre><p>This way, the main loop stays readable and easy to manage.</p><h4>2. Random Account Selection</h4><p>I used Python’s random.choice() to pick accounts dynamically:</p><pre>account_b = random.choice(data)</pre><ul><li>Ensures every round is different.</li><li>Prevents showing the same account twice in a row.</li></ul><h4>3. Looping for Game Rounds</h4><p>A while loop handles the game rounds:</p><pre>while game_should_continue:<br>    ...<br>    if is_correct:<br>        score += 1<br>        print(f&quot;You&#39;re right! Current score {score}&quot;)<br>    else:<br>        print(f&quot;Sorry, that&#39;s wrong. Final score: {score}.&quot;)<br>        game_should_continue = False</pre><ul><li>Keeps track of <strong>score</strong> and <strong>game state</strong>.</li><li>Ends the game immediately if the guess is wrong.</li></ul><h4>4. Making it Visual</h4><pre>print(&quot;\n&quot; * 20)</pre><ul><li>Clears the console between rounds.</li><li>Keeps the interface clean and easy to read.</li></ul><h4>5. What I Learned</h4><ul><li><strong>Breaking code into functions</strong> improves readability and reusability.</li><li><strong>Random selection</strong> keeps the game dynamic.</li><li>Using <strong>loops and conditionals</strong> effectively manages game flow.</li><li>Simple <strong>ASCII art</strong> can make CLI games more engaging.</li></ul><h4>🎯 Next Steps</h4><ul><li>Add <strong>more accounts</strong> for variety.</li><li>Implement <strong>difficulty levels</strong>.</li><li>Explore a <strong>graphical interface</strong> for the game.</li><li>Expand gameplay mechanics like <strong>streaks, lives, or timed rounds</strong>.</li></ul><p>Day 14 was <strong>super productive</strong>, and building this game helped me solidify <strong>Python basics, loops, functions, and decision-making</strong>. I’m excited to continue the journey and see what the next challenge brings! 🚀</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f312f8aba692" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 13 of 100 Days of Python: Beginner Debugging: How to Find and Fix Errors in your Code]]></title>
            <link>https://medium.com/@irorahmah/day-13-of-100-days-of-python-beginner-debugging-how-to-find-and-fix-errors-in-your-code-15294fa59f29?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/15294fa59f29</guid>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Thu, 18 Dec 2025 17:30:58 GMT</pubDate>
            <atom:updated>2025-12-18T17:30:58.366Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*RC9fjhw6C3097Sk2leAkIQ.png" /></figure><p>Debugging is an essential skill for every programmer. On <strong>Day 13 of my 100 Days of Python journey</strong>, I focused on learning <strong>how to find, understand, and fix bugs</strong> effectively. Today was all about sharpening my problem-solving skills, stepping through code like a computer, and learning practical strategies for keeping my Python programs error-free.</p><p>Here’s what I learned.</p><h3>1. Describe the Problem 📝</h3><p>Before diving into code, I made it a habit to <strong>clearly describe the problem</strong>. Writing down what’s happening and what I expect helps me understand why the code is failing.</p><pre># Problem: The loop never prints &quot;You got it&quot; when i reaches 20<br>def my_function():<br>    for i in range(1, 20):<br>        if i == 20:<br>            print(&quot;You got it&quot;)<br>my_function()</pre><h3>2. Reproduce the Bug 🔄</h3><p>If a bug exists, reproduce it consistently. Running the code multiple times or using sample inputs ensures you understand exactly when the bug happens.</p><pre>from random import randint</pre><pre>dice_images = [&quot;❶&quot;, &quot;❷&quot;, &quot;❸&quot;, &quot;❹&quot;, &quot;❺&quot;, &quot;❻&quot;]<br>dice_num = randint(1, 6)  # ❌ This can cause an IndexError<br>print(dice_images[dice_num])</pre><h3>3. Play Computer and Evaluate Each Line 🖥️</h3><p>Mentally step through the code like Python would. I track variable values and program flow, which often reveals logic errors before even running the code.</p><h3>4. Fix Errors and Watch for Red Underlines ✏️</h3><p>Modern IDEs highlight syntax or semantic errors. Paying attention to these <strong>red underlines</strong> saves a lot of frustration.</p><h3>5. Squash Bugs with a print() Statement 🐛</h3><p>Using print() strategically helps track <strong>what values variables have at different points</strong>. It’s simple but powerful.</p><pre>year = int(input(&quot;What&#39;s your year of birth? &quot;))<br>if year &gt; 1980 and year &lt; 1994:<br>    print(&quot;You are a millennial.&quot;)<br>elif year &gt;= 1994:<br>    print(&quot;You are Gen Z.&quot;)</pre><h3>6. Use try/except for Input Errors ⚠️</h3><p>User input can crash programs. Handling errors safely ensures <strong>program robustness</strong>.</p><pre>try:<br>    age = int(input(&quot;How old are you? &quot;))<br>except ValueError:<br>    print(&quot;Invalid input. Please enter a number.&quot;)<br>    age = int(input(&quot;Try again: &quot;))</pre><h3>7. Bring Out the BIG Gun: Using a Debugger 🕵️‍♂️</h3><p>For more complex bugs, stepping through code <strong>line by line</strong> with a debugger helps inspect variables and program flow without adding print statements everywhere.</p><h3>8. Rest Then Come Back 🛌</h3><p>Sometimes, taking a <strong>break</strong> clears your mind and helps you see bugs that were previously invisible. Fresh eyes = fresh perspective.</p><h3>9. Run Your Code Often ⚡</h3><p>Instead of writing hundreds of lines of code at once, I <strong>run small portions frequently</strong>. This prevents multiple bugs from piling up and makes debugging easier.</p><h3>10. Ask a Friend or Use Stack Overflow 🤝</h3><p>If stuck, don’t hesitate to <strong>ask peers or check online forums</strong>. Sometimes a fresh perspective solves a problem in minutes.</p><p>Debugging isn’t just about fixing code — it’s about <strong>thinking like a computer, being methodical, and having patience</strong>. Day 13 taught me that even the most frustrating bugs can be conquered with the right strategies.</p><h3>Code Exercise Snippet: Odd or Even</h3><pre>number = int(input(&quot;Enter a number: &quot;))<br>if number % 2 == 0:<br>    print(&quot;Even&quot;)<br>else:<br>    print(&quot;Odd&quot;)</pre><p>Debugging exercises like this helped reinforce <strong>line-by-line evaluation</strong>, which is key to writing error-free programs.</p><h4><strong>Takeaway</strong></h4><p>Debugging is a skill you build over time. The more you practice, the faster you’ll find and squash bugs, and the more confident you’ll become as a programmer.</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15294fa59f29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 12 of 100 Days of Python: Scope and Building a Number Guessing Game]]></title>
            <link>https://medium.com/@irorahmah/day-12-of-100-days-of-python-scope-and-building-a-number-guessing-game-e310e9159a9b?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/e310e9159a9b</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Tue, 16 Dec 2025 18:34:47 GMT</pubDate>
            <atom:updated>2025-12-16T18:34:47.600Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*17HqqiSQgQRfQMnYrTXC8w.png" /></figure><p>Day 12 was all about <strong>scope in Python</strong>, learning how variables live and die inside functions, and finally creating a fun <strong>Number Guessing Game</strong> as a hands-on project.</p><h4>Local vs Global Scope</h4><p>Understanding <strong>where your variables “live”</strong> is crucial in Python.</p><ul><li><strong>Local variables</strong> only exist inside the function where they are defined.</li><li><strong>Global variables</strong> exist everywhere in your program.</li></ul><p>For example:</p><pre>player_health = 10  # Global variable<br>def drink_potion():<br>    potion_strength = 2  # Local variable<br>    print(player_health)  # Accessible</pre><p>Here, potion_strength is only accessible inside the function, but player_health can be accessed anywhere. This is important because it helps prevent unexpected bugs.</p><h4>Modifying Global Variables</h4><p>If you want to modify a global variable inside a function, you have two options:</p><ol><li>Use the global keyword (less recommended).</li><li><strong>Return a new value</strong> and assign it back to the global variable.</li></ol><pre>enemies = 1<br>def increase_enemies(enemy):<br>    return enemy + 1<br>enemies = increase_enemies(enemies)<br>print(enemies)  # Output: 2</pre><p>Returning a value keeps your functions clean and predictable.</p><h3>Python Constants</h3><p>Python doesn’t have true constants, but by convention, variables written in <strong>all uppercase letters</strong> are treated as constants.</p><pre>PI = 3.14159<br>GOOGLE_URL = &quot;https://www.google.com&quot;</pre><p>These values should not be changed throughout the program.</p><h4>Prime Number Checker</h4><p>We practiced logic with <strong>loops and conditionals</strong> to check if a number is prime:</p><pre>def is_prime(num):<br>    if num == 2<br>        return True<br>    if num == 1:<br>        return False<br>    for i in range(2, num):<br>        if num % i == 0:<br>            return False<br>    return True<br>print(is_prime(73))  # True<br>print(is_prime(75))  # False</pre><p>This exercise reinforced how to combine loops, conditions, and function return values effectively.</p><h4>Final Project: Number Guessing Game</h4><p>The highlight of the day was building a <strong>Number Guessing Game</strong>.</p><p><strong>Game rules:</strong></p><ul><li>The computer generates a random number between 1 and 100.</li><li>The player keeps guessing until they get the right number.</li><li>The program provides feedback if the guess is too high or too low.</li><li>It counts the number of attempts.</li></ul><p>Here’s a peek at the code:</p><pre>from random import randint<br>number_to_guess = random.randint(1, 100)<br>attempts = 0<br>guess = 0<br>while guess != number_to_guess:<br>    guess = int(input(&quot;Guess the number between 1 and 100: &quot;))<br>    attempts += 1<br>    if guess &lt; number_to_guess:<br>        print(&quot;Too low.&quot;)<br>    elif guess &gt; number_to_guess:<br>        print(&quot;Too high.&quot;)print(f&quot;Congratulations! You guessed the number in {attempts} attempts.&quot;)</pre><p>By the end of this project, I felt more confident with:</p><ul><li><strong>Variable scopes</strong> (local vs global)</li><li>Using <strong>functions with return values</strong></li><li>Building <strong>interactive Python programs</strong></li></ul><h4>Key Takeaways</h4><ol><li>Always consider where your variables should live. Use local variables when possible to avoid conflicts.</li><li>Returning values from functions is often safer than modifying globals directly.</li><li>Small projects like a guessing game make learning Python practical and fun.</li></ol><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e310e9159a9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 11:Beginner the Black Jack Capstone Project]]></title>
            <link>https://medium.com/@irorahmah/day-11-beginner-the-black-jack-capstone-project-aab6913298b0?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab6913298b0</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Sat, 13 Dec 2025 18:01:53 GMT</pubDate>
            <atom:updated>2025-12-13T18:01:53.497Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*z0_NgIWo12YzwTUURwWJCw.png" /></figure><p>Day 11 of my Python journey focused on <strong>beginner to intermediate programming concepts</strong>, and we challenged ourselves with a real-world project, <strong>the Blackjack game</strong>. This project was both fun and a bit tricky because it combined <strong>functions, loops, lists, and conditionals</strong>.</p><h3>What We Learned Today</h3><h4>1. Functions that return values</h4><p>We continued practicing functions, this time with <strong>outputs using </strong><strong>return</strong>. For example:</p><pre>def add(a, b):<br>    return a + b<br>result = add(5, 3)<br>print(result)  # Output: 8</pre><p>Returning a value allows us to <strong>use the output elsewhere</strong>, making our programs modular and reusable.</p><h4>2. Randomness with Python</h4><p>We used the random module to simulate a deck of cards:</p><pre>import random<br>cards = [11, 2, 3, 4, 5, 6, 7, 8, 9, 10, 10, 10, 10]<br>card = random.choice(cards)<br>print(card)</pre><p>This let us <strong>draw cards randomly</strong> for both the user and computer3. Lists and Loops</p><p>We practiced <strong>storing hands as lists</strong> and <strong>looping through them</strong> to calculate scores.</p><pre>user_cards = [10, 7]<br>computer_cards = [11, 9]<br>for card in user_cards:<br>    print(card)</pre><h4>4. Logic for Blackjack</h4><p>The main challenge was implementing the rules:</p><ul><li>Jack, Queen, King = 10 points</li><li>Ace = 1 or 11 depending on the total</li><li>Check for <strong>Blackjack</strong> (Ace + 10 in first 2 cards)</li><li>Decide winner using conditional statements</li></ul><pre>if user_score &gt; 21:<br>    print(&quot;You went over. You lose 😭&quot;)<br>elif computer_score == 0:<br>    print(&quot;Computer has Blackjack. You lose 😱&quot;)</pre><h4>5. User Interaction &amp; Game Loop</h4><p>We used loops to let the user <strong>draw cards repeatedly</strong> until they pass or bust, and the computer automatically drew cards until it reached 17 or more.</p><pre>while not game_over:<br>    draw = input(&quot;Type &#39;y&#39; to get another card, type &#39;n&#39; to pass: &quot;)<br>    if draw == &quot;y&quot;:<br>        user_cards.append(deal_card())</pre><h3>Reflection</h3><p>This project was <strong>hands-on practice</strong> with Python fundamentals. It showed me how to combine:</p><ul><li>Functions</li><li>Lists</li><li>Loops</li><li>Conditionals</li><li>Randomness</li><li>User input</li></ul><p>I also realized that <strong>studying from a complete solution</strong> and then trying it myself is very effective for learning.</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab6913298b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 10: Beginner Functions with Outputs]]></title>
            <link>https://medium.com/@irorahmah/day-10-beginner-functions-with-outputs-47a7e4366e22?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/47a7e4366e22</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Tue, 09 Dec 2025 15:52:33 GMT</pubDate>
            <atom:updated>2025-12-09T15:52:33.616Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*rh3JpnHat-_WQPuoXDMNLA.png" /></figure><p>Today marks Day 10 of my <em>100 Days of Python</em>, and honestly, this is the day everything started to <em>click</em>. I finally moved from writing functions that <em>do something</em>… to writing functions that <em>return results, </em>and it completely changed how I think about programming.</p><p>Let me walk you through what I learned today, with a few snippets along the way.</p><h3>🔹 Functions With Outputs</h3><p>Before now, my functions could only <em>print</em>. But printing doesn’t give you control — returning does.</p><p>Here’s the moment everything clicked:</p><pre>def format_name(first, last):<br>    return f&quot;{first.title()} {last.title()}&quot;</pre><pre>result = format_name(&quot;BElla&quot;, &quot;KIck&quot;)<br>print(result)   # Bella Kick</pre><p>The return keyword felt like handing a value back to the rest of my code. It makes functions reusable and powerful.</p><h3>🔹 Multiple Return Paths</h3><p>Today, I also learned that a function can return <em>different things</em> depending on the situation. This makes code smart and flexible.</p><pre>def check_age(age):<br>    if age &lt; 0:<br>        return &quot;Invalid age&quot;<br>    elif age &lt; 18:<br>        return &quot;You are young!&quot;<br>    else:<br>        return &quot;Welcome!&quot;</pre><p>One function, multiple outcomes , clean and useful.</p><h3>🔹 Leap Year Challenge</h3><p>This was the brain-twister of the day.<br> The rules look simple… until you start writing them.</p><p>A year is a leap year if:</p><ul><li>divisible by <em>4</em> → yes</li><li>divisible by <em>100</em> → no</li><li>divisible by <em>400</em> → yes</li></ul><p>Here’s the function:</p><pre>def is_leap_year(year):<br>    if year % 4 == 0:<br>        if year % 100 == 0:<br>            if year % 400 == 0:<br>                return True<br>            else:<br>                return False<br>        else:<br>            return True<br>    else:<br>        return False</pre><p>It finally made sense once I followed the logic step by step.</p><h3>🔹 Docstrings</h3><p>I also learned about docstrings — little explanations inside functions that help your future self (and others) understand what the code does.</p><pre>def greet(name):<br>    &quot;&quot;&quot;Returns a friendly greeting with the user&#39;s name.&quot;&quot;&quot;<br>    return f&quot;Hello, {name}!&quot;</pre><p>It makes your code clean, readable, and professional.</p><h3>🔹 Function Quiz</h3><p>We did a short quiz to test whether we really understood:</p><ul><li>how return works</li><li>how code flows</li><li>how to write reusable functions</li></ul><p>It forced me to slow down and think through each line of code.</p><h3>🔹 The Calculator Project</h3><p>We wrapped up the day with a mini project: building our own calculator.<br> It used:</p><ul><li>a dictionary of operations</li><li>multiple functions</li><li>return statements</li><li>loops for continuous calculations</li></ul><p>Here’s a small piece of it:</p><pre>def add(n1, n2):<br>    return n1 + n2<br>operations = {<br>    &quot;+&quot;: add,<br>    &quot;-&quot;: subtract,<br>    &quot;*&quot;: multiply,<br>    &quot;/&quot;: divide,<br>}<br></pre><p>This was the most exciting part — seeing functions work together like real tools.</p><h3>⭐ Final Thoughts</h3><p>Day 10 has been one of the most eye-opening days so far.<br> Learning how to return values unlocked a new level of clarity for me. My programs feel more structured, more professional, and easier to maintain.</p><p>It finally feels like I’m not just writing code…<br> I’m <em>building logic</em>.</p><p>I can’t wait to see what Day 11 brings.</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47a7e4366e22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day-9 Beginner dictionaries nesting and secrets auction]]></title>
            <link>https://medium.com/@irorahmah/day-9-beginner-dictionaries-nesting-and-secrets-auction-f63cdd795a0d?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/f63cdd795a0d</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 18:40:28 GMT</pubDate>
            <atom:updated>2025-12-05T18:40:28.320Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*1YAGaPpAxrPLqispSIeOog.png" /></figure><p>Day 9 of the 100 Days of Python course was all about <strong>dictionaries</strong> — one of Python’s most powerful data structures. After today, I feel much more confident in using dictionaries not just for simple key-value pairs, but also for more complex, nested structures.</p><p>Here’s a breakdown of what I learned:</p><h3>1. What is a dictionary?</h3><p>A dictionary is a collection of key-value pairs. Think of it as a mini-database where each key points to a value.</p><pre>programming_dictionary = {<br>    &quot;Bug&quot;: &quot;An error in a program that prevents it from running as expected.&quot;,<br>    &quot;Function&quot;: &quot;A piece of code you can call over and over again.&quot;,<br>}</pre><p>You can retrieve a value simply by referring to its key:</p><pre>print(programming_dictionary[&quot;Function&quot;])</pre><p>And you can easily add new entries:</p><pre>programming_dictionary[&quot;Loop&quot;] = &quot;The action of doing something repeatedly.&quot;</pre><h3>2. Updating and clearing dictionaries</h3><p>If you want to update a value:</p><pre>programming_dictionary[&quot;Bug&quot;] = &quot;A moth in your computer.&quot;</pre><p>And if you need to wipe all data:</p><pre>programming_dictionary = {}</pre><h3>3. Looping through dictionaries</h3><p>Looping through dictionaries is straightforward:</p><pre>for key in programming_dictionary:<br>    print(key)<br>    print(programming_dictionary[key])</pre><p>This prints all the keys and their corresponding values.</p><h3>4. Nested structures</h3><p>Dictionaries can hold lists, and even other dictionaries!</p><p><strong>Nested list example:</strong></p><pre>nested_list = [&quot;A&quot;, &quot;B&quot;, [&quot;C&quot;, &quot;D&quot;]]<br>print(nested_list[2][1])  # Outputs:</pre><p><strong>Nested dictionary example:</strong></p><pre>travel_log = {<br>  &quot;France&quot;: {<br>    &quot;cities_visited&quot;: [&quot;Paris&quot;, &quot;Lille&quot;, &quot;Dijon&quot;],<br>    &quot;total_visits&quot;: 12<br>  },<br>  &quot;Germany&quot;: {<br>    &quot;cities_visited&quot;: [&quot;Berlin&quot;, &quot;Hamburg&quot;, &quot;Stuttgart&quot;],<br>    &quot;total_visits&quot;: 5<br>  },<br>}<br>print(travel_log[&quot;Germany&quot;][&quot;cities_visited&quot;][2])  # Outputs: Stuttgart</pre><h3>5. Practical project: Blind Auction</h3><p>Today’s mini-project was a <strong>blind auction</strong> simulation. Using dictionaries, I stored bidders and their bid amounts. Then, using a simple loop, I determined the highest bidder.</p><p>This exercise was a great way to <strong>apply dictionaries in a real-world scenario</strong> and reinforce my understanding of loops and conditionals.</p><h3>Key Takeaways</h3><ul><li>Dictionaries are ideal for storing key-value pairs.</li><li>You can nest lists and dictionaries for more complex data.</li><li>Loops make it easy to iterate through dictionaries.</li><li>Combining dictionaries with user input allows for dynamic, real-world applications, like a blind auction.</li></ul><p>Day 9 made me realize just how versatile dictionaries are. From storing basic information to building mini-applications, mastering dictionaries is a huge step in Python programming!</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f63cdd795a0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 8 — Functions, Love Calculator, and Caesar Cipher]]></title>
            <link>https://medium.com/@irorahmah/day-8-functions-love-calculator-and-caesar-cipher-1d4ce731d2d0?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d4ce731d2d0</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Tue, 02 Dec 2025 16:16:45 GMT</pubDate>
            <atom:updated>2025-12-02T16:16:45.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*TMebnaeJKqNDWp9j338Uiw.png" /></figure><h3>Day 8 — Functions, Love Calculator, and Caesar Cipher</h3><p>Today’s Python session was all about <strong>functions with inputs, argument types, and building interactive programs</strong>. We explored a variety of exercises that combined creativity with logic, making coding both practical and fun. Here’s a breakdown of what we learned:</p><h3>1️⃣ Functions with Inputs</h3><p>Functions let us <strong>avoid repeating code</strong>. Today, we learned how to pass <strong>inputs to functions</strong> using parameters. For example, instead of always printing &quot;Hello&quot;, we can write a function that greets anyone by name:</p><pre>def greet_with(name, location):<br>    print(f&quot;Hello {name}&quot;)<br>    print(f&quot;How is it like over there in {location}?&quot;)</pre><p>We also explored <strong>positional vs keyword arguments</strong></p><ul><li><strong>Positional:</strong> Arguments must be in the correct order.</li><li><strong>Keyword:</strong> Arguments can be passed in any order by naming them.</li></ul><h3>2️⃣ Life in Weeks</h3><p>Inspired by Tim Urban’s <em>“Your Life in Weeks”</em>, we wrote a program that calculates <strong>how many weeks you have left if you live until 90</strong>:</p><pre>def life_in_weeks(age):<br>    weeks_left = (90 - age) * 52<br>    print(f&quot;You have {weeks_left} weeks left.&quot;)</pre><p>It was a simple exercise, but it made us realize how <strong>functions can be used to perform calculations and return results dynamically</strong>.</p><h3>3️⃣ Love Calculator</h3><p>Next, we created a fun <strong>Love Calculator</strong> that calculates a compatibility score between two names:</p><ol><li>Count the letters in &quot;TRUE&quot; in both names.</li><li>Count the letters in &quot;LOVE&quot; in both names.</li><li>Combine the counts to create a score.</li></ol><p>Example:</p><pre>calculate_love_score(&quot;Kanye West&quot;, &quot;Kim Kardashian&quot;)</pre><p>This taught us <strong>string manipulation, counting characters</strong>, and <strong>building creative programs</strong> using functions.</p><h3>4️⃣ Caesar Cipher</h3><p>The highlight of the day was the <strong>Caesar Cipher</strong>, a simple encryption technique. We learned how to:</p><ul><li><strong>Encrypt messages</strong> by shifting letters forward.</li><li><strong>Decrypt messages</strong> by shifting letters backward.</li><li>Organize our code into a single caesar() function that <strong>handles both encryption and decryption</strong>.</li></ul><p>Example:</p><pre>caesar(text=&quot;hello&quot;, shift=3, direction=&quot;encode&quot;)</pre><p>This exercise reinforced <strong>loops, indexing, modular arithmetic</strong>, and <strong>string operations</strong>, showing how functions can be combined to build complex logic.</p><h3>5️⃣ Key Takeaways</h3><ul><li>Functions make code <strong>reusable and organized</strong>.</li><li><strong>Parameters and arguments</strong> allow dynamic behavior.</li><li>Creative exercises like the <strong>Love Calculator</strong> and <strong>Caesar Cipher</strong> make learning Python exciting.</li><li>Proper <strong>code organization</strong> helps in combining multiple functions into a clean workflow.</li></ul><p>Day 8 was a perfect mix of <strong>logic, creativity, and Python fundamentals</strong>, and it gave us a strong foundation for building interactive and fun programs.</p><p>You can check out the full code and project structure on my <a href="https://github.com/Rahma-Iro/100-days-of-python">https://github.com/Rahma-Iro/100-days-of-python</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d4ce731d2d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Cybersecurity Matters Now More Than Ever — Especially for Young Africans]]></title>
            <link>https://medium.com/@irorahmah/why-cybersecurity-matters-now-more-than-ever-especially-for-young-africans-ab1fa08c7c73?source=rss-2de09eb7e695------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab1fa08c7c73</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[africa]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Rahma Nasir Iro]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 22:01:18 GMT</pubDate>
            <atom:updated>2025-12-01T22:02:09.542Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1MonC5F27yGxtdfTuWq8vQ.jpeg" /></figure><h3>Why Cybersecurity Matters Now More Than Ever — Especially for Young Africans</h3><p>Over the last few years, I’ve noticed something interesting: our lives have quietly moved online without us even realizing just how deep the shift has gone. We pay bills with our phones, keep our memories on Google Photos, run small businesses on WhatsApp, share personal details on apps we barely know, and trust the internet more than we trust some people.</p><p>It’s beautiful and scary at the same time.</p><p>The more digital we become, the more vulnerable we are. And that’s where cybersecurity comes in. Not as a “tech buzzword,” but as a real part of everyday life that affects all of us.</p><p>I’m not writing this as an expert. I’m writing this as someone who is learning, someone who cares, and someone who believes young Africans deserve to understand the world they’re stepping into.</p><h3>The truth is simple: the internet grew faster than our security</h3><p>Africa is experiencing massive digital growth, maybe the fastest in the world. But the sad part? Our cybersecurity awareness didn’t grow with it.</p><p>We got:</p><p>• cheaper smartphones</p><p>• more digital banking</p><p>• online businesses popping up everywhere</p><p>• remote work</p><p>• AI tools</p><p>• mobile money</p><p>But many people still use “12345” as their password.</p><p>It’s not our fault. Nobody taught us digital security the same way they taught us maths or English. But we are the ones paying the price when things go wrong.</p><h3>Cyber threats today don’t look like the movies</h3><p>Sometimes when people hear “cybersecurity,” they imagine a hacker in a dark room with green codes on their screen. But the reality in 2025 is completely different.</p><h3>1. Hackers now use AI</h3><p>Yes — AI helps them write believable messages, break weak passwords, and scan systems faster than any human could.</p><h3>2. Ransomware is everywhere</h3><p>Hospitals, schools, small shops, nobody is too small to be attacked.</p><h3>3. Social engineering is the biggest threat</h3><p>Most cyber attacks don’t happen because computers are weak.<br> They happen because humans are trusting.</p><p>A simple phone call or fake link is enough.</p><h3>Why this matters so much for Africa</h3><p>We are a very young continent — and a very digital one. Millions of people connect every year, sometimes without even the basics of cyber hygiene. That makes us a big target.</p><p>But here’s the twist:<strong><br> It also makes cybersecurity one of the biggest opportunities for African youth.</strong></p><p>There are not enough cyber professionals globally, and Africa feels that shortage the most.</p><p>Young people who learn cybersecurity now won’t just be “tech people.”<br> They will be:</p><p>• protectors of digital communities</p><p>• guardians of online businesses</p><p>• defenders of national data</p><p>• solution-builders for local problems</p><p>• And most importantly, they will be the generation that shapes a safer digital future.</p><h3>You don’t need to be a genius to start</h3><p>This is something I wish more people knew.</p><p>Cybersecurity is not just for coding gurus. The field is wide — you can be good at analysis, writing policies, investigating digital evidence, teaching awareness, or even understanding human psychology.</p><p>If you’re curious, detail-oriented, or you simply like solving problems, you belong here.</p><p>Here’s how to start small:</p><h3>1. Learn the basics</h3><p>The internet, threats, digital hygiene, strong passwords, updates — the simple things matter.</p><h3>2. Explore without pressure</h3><p>Try a bit of ethical hacking, cloud security, GRC, digital forensics, etc.<br> You’ll naturally discover what you enjoy.</p><h3>3. Create something</h3><blockquote>Write about a phishing email you noticed.<br> Test your own Wi-Fi security.<br> Share a lesson you learned.</blockquote><p>Small projects show more passion than certificates sometimes.</p><h3>4. Join a community</h3><p>CyberGirls, OWASP, ISACA, WiCyS, local tech groups — being around learners helps.</p><h3>My personal belief</h3><p>• I think cybersecurity is not just about computers,it’s about people.</p><p>• It’s about protecting someone’s savings.</p><p>• It’s about making sure a small business in Kano or Nairobi or Accra doesn’t lose everything because of one link.</p><p>• It’s about giving young people the confidence to grow online without fear.</p><p>• It’s about making technology safer for everyone, especially those who don’t know how to protect themselves.</p><p>And the best part?<br> You don’t have to wait until you are an expert.<br> You can start learning, practicing, and sharing knowledge today.</p><h3>Final thoughts</h3><p>Technology is moving fast, whether we’re ready or not.<br> Cybersecurity is our seatbelt in this digital world. It doesn’t stop the journey, it simply makes it safer.</p><p>As young Africans, we have a rare opportunity to build our skills now and become the leaders who shape digital safety tomorrow. The continent needs us.</p><p>And honestly?<br> The future of cybersecurity in Africa will be shaped by curious minds, brave learners, and people who care, people like you and me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab1fa08c7c73" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>