<?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 Idogwu ogechukwu Luciana on Medium]]></title>
        <description><![CDATA[Stories by Idogwu ogechukwu Luciana on Medium]]></description>
        <link>https://medium.com/@idogwuogechi?source=rss-becda74f8d29------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4TXjnWGLCEoM8D4HoZmLUg.jpeg</url>
            <title>Stories by Idogwu ogechukwu Luciana on Medium</title>
            <link>https://medium.com/@idogwuogechi?source=rss-becda74f8d29------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:29:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@idogwuogechi/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[Week 7 of My Data Science Internship| Visualizing data]]></title>
            <link>https://medium.com/@idogwuogechi/week-7-of-my-data-science-internship-visualizing-data-e64ad58e2c7c?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/e64ad58e2c7c</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[pandas]]></category>
            <category><![CDATA[matplotlib]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 21:02:47 GMT</pubDate>
            <atom:updated>2026-10-25T21:02:47.416Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N02Xnc6vk1InldNw" /><figcaption>Photo by <a href="https://unsplash.com/@lukechesser?utm_source=medium&amp;utm_medium=referral">Luke Chesser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>It’s week 7 of my data science internship, and this week was all about messy data.</p><p>This article covers everything I worked on in week 7.</p><p><strong>Table of Contents:</strong></p><p>· Cleaning messy data<br> · Selecting and filtering data<br> · Visualizing data<br> · Combining data<br> · SQL practice<br> · Holiday weather project<br> · GDP and life expectancy project<br> · Challenges I faced and how I solved them<br> · Lesson from this week<br> · Key takeaways</p><p><strong>Cleaning Messy Data 🧹</strong></p><p>The London weather data came straight from the original export, and the mess was left in on purpose. Three problems needed fixing:</p><p>· Column names had extra spaces at the start, like &quot; Mean Humidity&quot;. I fixed them with london.columns.str.strip().<br> · The last column was named WindDirDegrees&lt;br /&gt;, and every value ended in &lt;br /&gt;, leftovers from a web page. I renamed the column, removed the tags with .str.replace(), and converted the values to integers.<br> · Dates were stored as plain text. I converted them with pd.to_datetime() and made them the index.</p><p>Making the date the index is like putting a date label on every row. After that, I could ask for “all of April” and pandas understood.</p><pre># 1. strip leading spaces from column names<br>london.columns = london.columns.str.strip()<br><br># 2. fix the &lt;br /&gt; column and its values<br>london = london.rename(columns={&quot;WindDirDegrees&lt;br /&gt;&quot;: &quot;WindDirDegrees&quot;})<br>london[&quot;WindDirDegrees&quot;] = (<br>    london[&quot;WindDirDegrees&quot;].astype(str).str.replace(&quot;&lt;br /&gt;&quot;, &quot;&quot;, regex=False)<br>)<br>london[&quot;WindDirDegrees&quot;] = london[&quot;WindDirDegrees&quot;].astype(int)<br><br># 3. make GMT a real date and use it as the index<br>london[&quot;GMT&quot;] = pd.to_datetime(london[&quot;GMT&quot;])<br>london = london.set_index(&quot;GMT&quot;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*R3w-ZBBJ7XBVAogA9-MuHA.png" /></figure><p><strong>Selecting and Filtering Data 🔍</strong></p><p>With a date index, I could slice rows by date:</p><pre>london.loc[&quot;2014-04-01&quot;:&quot;2014-04-11&quot;]</pre><p>I also filtered with conditions. Northerly wind wraps around the compass (350° to 10°), so I used “or” instead of “between”:</p><pre>london[(london[&quot;WindDirDegrees&quot;] &gt;= 350) | (london[&quot;WindDirDegrees&quot;] &lt;= 10)]</pre><p>To find missing values I used .isna(). The gust speed column had only 131 values out of 365 days, so I stopped relying on it.</p><p><strong>Visualising Data 📊</strong></p><p>I plotted humidity through spring and drew a chart with temperature as a line and rainfall as bars on a second axis. Highlighting my chosen weeks as gold bands made the result easy to read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1B5ABla63gBcmakLKLdR0Q.png" /></figure><p><strong>Combining Data 🔗</strong></p><p>I used pd.merge() to join two tables on the country column. An inner join works like a guest list: only countries on both lists get in. That&#39;s why rows with missing values disappear.</p><p>To measure whether two things move together, I used the Spearman correlation. It compares rankings instead of raw values, so it isn’t thrown off by huge outliers like the US economy. A scatterplot shows what the number can’t.</p><p><strong>SQL Practice 🗄️</strong></p><p>I redid the same jobs in SQL:</p><p>· REPLACE and TRY_CAST to clean the wind column<br> · TRY_CONVERT and BETWEEN to filter a date range<br> · JOIN to combine tables, and LEFT JOIN to count the rows lost<br> · A window function to find the driest 7-day stretch of summer</p><p><strong>Holiday Weather Project ☀️</strong></p><p><strong>London 2014:</strong> I filtered to June, July and August, averaged the weather by full week, and ranked the weeks by rain and temperature. My two picks were <strong>30 June to 6 July</strong> and <strong>14 to 20 July</strong>, which averaged 27.4 °C with only 0.51 mm of rain.</p><p><strong>Brasília 2023:</strong> For the BRICS version I downloaded 2023 data for Brasília. Ten different weeks between May and August had zero rain. Using a rolling 14-day window, the best two weeks were <strong>11 to 24 August</strong>, with an average high of 28.8 °C and no rain at all. Brasília’s long dry season makes the choice easy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OUN-PGiAnkfbERMBW-F39w.png" /></figure><p><strong>GDP and Life Expectancy Project 🌍</strong></p><p>Do richer countries live longer?</p><p>· Total GDP vs life expectancy: correlation of <strong>0.50</strong>, a moderate link.<br> · Only <strong>France and Japan</strong> appeared in both the top ten by GDP and the top ten by life expectancy.<br> · <strong>Nigeria and South Africa</strong> had high total GDP but life expectancy below 60. Their populations are large, so the wealth is spread thin.<br> · GDP <strong>per person</strong> vs life expectancy: correlation of <strong>0.85</strong>, much stronger.<br> · For my own project I tested population vs life expectancy and got <strong>-0.09</strong>, not significant. How many people live in a country says almost nothing about how long they live.</p><p>The suggested PPP indicator wasn’t in our database, so I used GDP per capita and noted the limitation.</p><pre>df[&#39;GDP per capita (£)&#39;] = df[GDP] * 1_000_000 / df[&#39;population&#39;]<br>PC = &#39;GDP per capita (£)&#39;<br><br>corr, p = spearmanr(df[PC], df[LIFE])<br>print(&#39;Correlation:&#39;, corr, &#39;| significant&#39; if p &lt; 0.05 else &#39;| not significant&#39;)<br><br>df.plot(x=PC, y=LIFE, kind=&#39;scatter&#39;, grid=True, logx=True, figsize=(10, 4))</pre><pre>Correlation: 0.8503040098920375 | significant</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/841/1*xNryAXhtsLMZcLvvGMnRQw.png" /><figcaption>Image showing GDP per capita</figcaption></figure><p><strong>Challenges I Faced and How I Solved Them</strong></p><p><strong>1. The partial week trap ⚠️</strong></p><p>My first ranking put a “week” with 0 mm of rain at the top. It was a single day, because 1 June fell on a Sunday. I counted the days in each week and kept only full weeks.</p><p><strong>2. A tiny typo with a big error</strong></p><p>merge is not defined. I had forgotten the pd. in front of it. The error message told me exactly what was wrong and I fixed it.</p><p><strong>3. The year didn’t match 📅</strong></p><p>The project text said 2023, but the London data was from 2014. I checked the data and used what was really there.</p><p><strong>4. The data I needed wasn’t there</strong></p><p>The PPP indicator didn’t exist in the database. I used the closest alternative and explained the difference.</p><p><strong>Lesson from this week</strong></p><p>Cleaning isn’t a warm-up before the real analysis. It is most of the analysis. A week with a wrong average or a missing day can look perfectly normal. Checking the counts and cross-checking the same result a second way (SQL vs pandas) caught problems that no error message would have.</p><p><strong>Key takeaways:</strong></p><p><em>.str.strip() = removes the extra spaces from column names.<br> </em><em>pd.to_datetime() = turns text into real dates, so you can filter by month or date range.<br> </em><em>resample(&quot;W&quot;) = groups daily data into weekly summaries.<br> Inner join = keeps only the rows that exist in both tables.<br> Spearman correlation = measures whether two things rise together, using rankings.<br> Per capita = divide by population before comparing countries.<br> Always check the data = count your rows and days, and trust nothing that looks too tidy.</em></p><p>Thank you for reading up to this point. Please leave a like and comment if you found this article helpful. See you next week 👋. Until then, Happy Coding ✨.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e64ad58e2c7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Data Science Journey | Week 6| Pandas| Numpy]]></title>
            <link>https://medium.com/@idogwuogechi/my-data-science-journey-week-6-pandas-numpy-063b481888ca?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/063b481888ca</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[numpy]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[pandas]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 18:20:08 GMT</pubDate>
            <atom:updated>2026-10-19T18:20:08.683Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>My Data Science Journey | Week 6| Pandas| Numpy</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uUdVqc7dYeixY8Q4" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>‎It’s week 6 of my data science internship, and this week, I worked with a real database to analyze the data and uncover valuable insights. <br>‎<br>‎This article covers everything I worked on in week 6.<br>‎<br>‎Table of Contents:<br>‎<br>· ‎Connecting Python to a database<br>· ‎NumPy and pandas<br>· ‎Intermediate SQL<br>· ‎Weather analysis project<br>· ‎Challenges I faced and how I solved them<br>· ‎Lesson from this week<br>· ‎Key takeaways<br>‎<br>‎<strong>Connecting Python to a Database:</strong><br>‎<br>‎Until now, the data I worked with came as files. This week, the data lived on a company server, and I had to ask for it.<br>‎<br>‎The first question I asked myself was, how do I log in without putting my password in my code?<br>‎<br>‎The answer is a .env file 🔐. Think of it as a locked drawer for your secrets. Your code opens the drawer when it needs a password, but the password is never written inside the code itself.</p><pre>SQL_SERVER_NAME=...<br>‎SQL_SERVER_DATABASE=...<br>‎SQL_READONLY_USERNAME=...<br>‎SQL_READONLY_PASSWORD=...</pre><p>‎<br>‎Then I added .env to a file called .gitignore. It tells Git, <em>&quot;never upload these files.&quot;</em> Without it, my password would have gone to GitHub the moment I pushed my project.<br>‎<br>‎A helper file, dataraflow_db.py, reads the .env file and gives me one function:</p><pre>df = run_query(&quot;SELECT * FROM week06.london_2014&quot;)<br>df.head()</pre><p>output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*S_-lXb8V6h23z9izS8M29Q.png" /><figcaption>image showing part of the dataframe</figcaption></figure><p>‎It runs any SQL query and hands me the result as a pandas DataFrame. This is also where last week’s lesson on modules became useful, because I could import it into any notebook.<br>‎<br><strong>‎NumPy and pandas</strong><br>‎<br>‎NumPy 🔢 is Python’s tool for fast number work. It is a tool that helps Python work with lots of numbers at once.This week I practiced:<br>‎<br>· ‎Checking for missing values with np.isnan()<br>· ‎Comparing arrays with a tolerance using np.allclose()<br>· ‎Finding how much memory an array uses<br>‎<br>‎pandas 🐼 is where the data analysis happens. pandas is like a spreadsheet you control with code. This week I learnt how to:<br>‎<br>· ‎Pick a row with df.iloc[54]<br>· ‎Select columns with df[[&quot;Country&quot;, &quot;TB deaths&quot;]]<br>· ‎Filter with conditions, for example:</p><pre>‎<br>df[(df[&quot;Population (1000s)&quot;] &lt;= 50000) | (df[&quot;TB deaths&quot;] &gt;= 20000)][[&quot;Country&quot;]]</pre><p>output:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*HtKeiI1saVZ4LXIzs5b6rQ.png" /></figure><p>‎I also practiced pandas Series, which are like one column of a table, and converted them to and from lists, dictionaries and NumPy arrays.<br>‎<br><strong>‎Intermediate SQL</strong><br>‎<br>‎Last week was SQL basics. This week was SQL with the training wheels off. Here are the ideas I used the most:<br>‎<br><strong>‎GROUP BY + HAVING</strong><br>‎<br>‎WHERE filters rows before grouping, and HAVING filters after. I used it to find countries that bought UK milk in all 12 months of 2014:<br>‎<br>‎HAVING COUNT(DISTINCT Period) = 12<br>‎<br><strong>‎JOIN and anti-join</strong> 🔗<br>‎<br>‎I joined WHO tuberculosis data to World Bank population data to calculate TB deaths per 100,000 people. An anti-join is the opposite question: &quot;which rows have no match?&quot; I used it to find the countries that failed to join.<br>‎<br><strong>‎UNION ALL</strong><br>‎<br>‎It stacks tables on top of each other. I used it to combine the weather tables of six cities into one.<br>‎<br><strong>‎CTEs and window functions</strong> 🪟<br>‎<br>‎A CTE is a temporary named result you build inside your query. A window function, like ROW_NUMBER() or a running total, looks across rows without collapsing them. I used both to find the hottest day of each month in London.<br>‎<br><strong>‎Weather Analysis Project</strong><br>‎<br>‎For the open-ended part of the assessment, I combined daily 2014 weather from six airports (Beijing, Brasília, Cape Town, Delhi, London and Moscow) into one table of 2,190 rows.<br>‎<br>‎What I found:<br>‎<br>· ‎Brasília was the warmest on average and the steadiest through the year. Moscow was the coldest and varied the most.<br>· ‎Cape Town’s seasons are the mirror image of the northern cities. Its warmest month was February and its coldest was July. That makes sense, because it’s in the southern hemisphere 🌍<br>· ‎London had the most rainy days, but Beijing had the single wettest day.<br>· ‎When I pooled all six cities together, temperature, humidity and rainfall were only weakly related. Mixing six different climates hides the patterns inside each one.<br>‎<br>‎I also found data that looked suspicious. Delhi’s January temperatures dropped to about -17°C, and Moscow’s rainfall column was zero for the entire year. I can’t say what caused it without checking the original source, but I flagged both as unreliable instead of building conclusions on them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*6w4d3YfxSBIbQSztYpS9Yw.png" /></figure><p><strong>‎<br>‎Challenges I Faced and How I Solved Them</strong><br>‎<br>‎This week was a lot of &quot;why isn’t this working?&quot; Here are the biggest ones.<br><strong>‎<br>‎1. The firewall blocked me </strong>🚧<br>‎<br>‎My first query failed with error 40615. My code was fine. The server’s firewall didn’t recognize my IP address.<br>‎<br>‎I had to send my IP address to the admins to be whitelisted to be able to access the database. <br>‎<br><strong>‎2. PendingRollbackError</strong><br>‎<br>‎An earlier query had timed out, and my connection got stuck.<br>‎<br>‎I had to restart the kernel and run the setup cell again.<br>‎<br><strong>‎3. Column names that didn’t match</strong><br>‎<br>‎London’s date column was called GMT, while the other cities called it Date. I also guessed other column names wrongly, like &#39;Export&#39; when the data said &#39;Exports’.<br>‎<br>‎I stopped guessing and explored the tables using the code:<br>‎<br>‎SELECT TOP 5 * FROM table_name<br><strong>‎<br>‎4. The integer division trap</strong> ⚠️<br>‎<br>‎Temperatures were stored as whole numbers, so SQL Server returned whole-number averages. A churn rate of 0.27 would show as 0.<br>‎<br>‎I had to cast to a decimal first, using CAST(x AS FLOAT) or 100.0 * x.<br>‎<br><strong>‎5. Names that don’t match</strong><br>‎<br>‎28 WHO countries failed to join with the World Bank table. &quot;Viet Nam&quot; vs &quot;Vietnam&quot;, &quot;Republic of Korea&quot; vs &quot;Korea, Rep.&quot;, &quot;Slovakia&quot; vs &quot;Slovak Republic&quot;. A join compares exact text, so one different character means no match.<br>‎<br>‎<br><strong>‎6. A result that was too perfect</strong><br>‎<br>‎In the loan data, every Rural application had a 0% approval rate and every Urban and Semi urban application had 100%. Real lending data never looks like that. It probably means there was a mistake somewhere.<br>‎<br>‎I wrote down my suspicions and what I’d tell the Head of Credit before anyone trains a model on it.<br>‎<br>‎<br>‎<br><strong>‎Lesson from this week.</strong><br>‎<br>‎This week was a lot to take in, it taught me that writing the query is the easy part. The real skill is checking whether the result makes sense.<br>‎<br>‎A query can run with no errors and still give you wrong answers: a truncated average, a join that quietly drops rows, or data that is too clean to be real.<br>‎<br><strong>‎Key takeaways</strong>:<br>‎<br><em>‎.env file = a safe place to keep passwords and keys out of your code.<br>‎.gitignore = tells Git which files to never upload.<br>‎HAVING = filters groups after grouping, where WHERE filters rows before.<br>‎JOIN = combines tables, and anti-join = finds the rows with no match.<br>‎Integer division = SQL Server keeps whole numbers unless you cast to decimal.<br>‎Always check the data = if a result looks too perfect or too strange, investigate it before trusting it.</em><br>‎<br>‎<br>‎Thank you for reading up to this point. Please leave a like and comment if you found this article helpful. See you next week 👋. Until then, Happy Coding ✨.<br>‎</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=063b481888ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[‎My Journey to Finding My First Research Topic: From Rejection to Acceptance | Data Science…]]></title>
            <link>https://medium.com/@idogwuogechi/my-journey-to-finding-my-first-research-topic-from-rejection-to-acceptance-data-science-4b2e5477f7f1?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b2e5477f7f1</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 21:30:08 GMT</pubDate>
            <atom:updated>2026-10-12T21:30:08.699Z</atom:updated>
            <content:encoded><![CDATA[<p>‎<strong>My Journey to Finding My First Research Topic: From Rejection to Acceptance | Data Science Internship, Week 5.</strong></p><figure><img alt="The Things You Need" src="https://cdn-images-1.medium.com/max/1024/0*f0q-IAIS4OvundW2" /><figcaption>Photo by <a href="https://unsplash.com/@sadswim?utm_source=medium&amp;utm_medium=referral">ian dooley</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>‎I have always wanted to publish a research paper, but I never really had the opportunity to begin one until I joined Dataraflow, where publishing a research paper was a prerequisite for graduation.<br>‎</p><p>‎Welcome to Week 5 of my data science internship. This week was about finding a research topic and drafting a research proposal.<br>‎<br>‎<br>‎To be honest, I was really excited when I realized I would have to publish a research paper because this was something I had always wanted to do.<br>‎<br>‎<br>‎But here came the challenge: I was supposed to identify a problem in my niche and figure out how data and AI could help solve it.<br>‎<br>‎<br>‎At first, I was stuck. I had no idea what I wanted to work on. Since I am in healthcare, the challenge was identifying the exact problem I wanted to solve and figuring out how to connect it with AI. I spent days researching, yet I still couldn’t come up with anything.<br>‎</p><p><strong>The Breakthrough.</strong><br>I realized I was doing it all wrong. For someone who did not already have a research area in mind, scrambling for ideas online was not going to work. I had to break it down into bits and ask myself certain questions:</p><p><strong>1. What are the different things Machine Learning (ML) can do?</strong></p><p>ML can perform classification, regression, clustering, prediction, forecasting, reinforcement learning, NLP and more. After understanding these concepts, I had to decide which one resonated with me most. Prediction has always fascinated me in data science, so I decided that whatever problem I was going to solve would be in relation to prediction. Now I had to find the problem, and that led me to my next question.</p><p><strong>2. What are my areas of interest in health?</strong></p><p>I knew I would love to explore diseases like HIV, malaria, sickle cell and cancer. So which one should I pick? I did some research on each of them, looking at past prediction works in literature and its gaps. In the process of this search, I found my eureka moment! 🥹</p><p><strong>The Turning Point.</strong></p><figure><img alt="Hold My Hand" src="https://cdn-images-1.medium.com/max/1024/0*mKHXeekpsrT6iiqz" /><figcaption>Photo by <a href="https://unsplash.com/@cashmacanaya?utm_source=medium&amp;utm_medium=referral">Cash Macanaya</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A few months ago, I worked on a project to predict crises in sickle cell patients, and it just clicked that my research should probably be in this area. But I wanted something more specific, so I decided to narrow it down to understanding how climate variations affect sickle cell patients, based on the number of hospital admissions in a teaching hospital in southeastern Nigeria.</p><p>I could not describe my joy when I finally put this topic together. It felt like the work had already been accepted for publication 😂. I was so proud of myself.</p><p>First, the topic was novel: not enough work has been done on how climate variations in sub-Saharan Africa, especially Nigeria, affect sickle cell patients.</p><p>Second, this is an area I am very interested in.</p><p>Third, if done right, this research can help the hospital predict crises months ahead of time, helping them prepare for emergencies and prevent stock outs or shortages of essentials.</p><p>But that joy faded when my topic was rejected 🤧</p><p><strong>The Redirection.</strong><br>Yes, my topic was rejected 🤧. Why? I was surprised myself.</p><p>It turns out I did not explicitly outline the scope of my research.</p><p>The issue of ethical approval wasn’t addressed; the data access was vague; the sample size wasn’t stated; the specific climate features I was measuring weren’t identified; the climate data source wasn’t outlined, and so on.</p><p>That was when I realized it’s one thing to find a research topic and another to check the feasibility of the study before you begin. A good idea can still hit a wall if constraints make it impossible to carry out.</p><p>It took me a few more days of research to properly answer those questions and resubmit the topic. And guess what? It was accepted 🤭.</p><p>To be honest, I am glad it was rejected the first time because it helped me step back and realize the magnitude of work this project requires, and whether I really wanted to do it. Resubmitting felt like a confirmation: <em>yes, I am willing to do this.</em></p><p>That is my journey to getting my first research topic.</p><p><strong>Research Proposal.</strong><br>After getting your research topic, the next step is drafting your research proposal. It serves as a blueprint for everything you’ll be doing.</p><p>The basic outline of a research proposal:</p><ul><li>1. Title: concise and descriptive.<br>2. Abstract: a concise summary of the problem, motivation, methods, expected results and contributions (written last).<br>3. Introduction/Background: what the problem is, why it matters, and the context a reader needs to care.<br>4. Literature Review: what’s already known and, critically, where the gap is.<br>5. Problem Statement: the gap stated plainly.<br>6. Research Questions/Hypotheses: the specific, answerable questions.<br>7. Objectives: what the study will accomplish, usually 3-5 points.<br>8. Methodology: the heart of the research. Be explicit. It contains:<br>• Research design (qualitative, quantitative or mixed)<br>• Population and sampling strategy<br>• Data collection instruments<br>Analysis approach<br>• Ethical considerations and approvals<br>9. Significance/Contribution: who benefits and how.<br>10. Limitations and Scope: what you’re deliberately not covering, and known constraints.<br>11. Timeline: usually a Gantt chart or phased table.<br>12. References.</li></ul><p>And that’s all for week 4 &amp; 5. I am glad I am really doing this. If there’s one thing I’m learning, it’s that you have to find what you really want to do and be willing to do the work. Research is interesting and has its benefits, but it takes effort.</p><p>I hope this story helps you start your research journey if you’re still unsure where to begin.</p><p>See you next week, until then, happy coding 👋🧑‍💻.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b2e5477f7f1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 3 as a Data science Intern.]]></title>
            <link>https://medium.com/@idogwuogechi/week-3-as-a-data-science-intern-35121e2389d4?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/35121e2389d4</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[python-module]]></category>
            <category><![CDATA[python-programming]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 12:53:40 GMT</pubDate>
            <atom:updated>2026-09-27T15:45:59.429Z</atom:updated>
            <content:encoded><![CDATA[<p>Week 3 as a Data science Intern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9OYYZTaDxHfe_RjH53IPTA.png" /></figure><p>It’s week 3 of my data science internship and it’s amazing how some concepts are becoming less strange.</p><p>This article covers everything I worked on in week 3.</p><p>Table of Contents:</p><ul><li>Python modules</li><li>Pip, Try…Except, User Input, VirtualEnv</li><li>Read and write files</li><li>Intro to SQL (Structured Query Language.</li><li>Lesson from this Week.</li><li>Key take-aways</li></ul><h3>Python Modules.</h3><p><em>A module is a single Python file (.py) containing code — functions, classes, variables , that you can import and reuse.</em></p><p>A module is like a toolbox 🧰, you need a module when you want to use code that has already been written and organized somewhere else instead of writing everything yourself.</p><p><strong>Why are modules useful:</strong></p><p>1. Reuse code — you can write something once and use it in many programs.<br>2. Saves time — Python and other developers have already created many useful functions so you don’t have to start writing them from scratch. <br>3. Keep code organized — Instead of putting everything in one huge file, related code can be separated into modules.<br>4. Add functionality — Modules give Python abilities that aren’t available through basic syntax alone.</p><p>For example, Python has a built-in <strong>math</strong> module containing useful mathematical tools example is the sqrt which allows you to take the square root of a number.</p><pre>import math</pre><pre>print(math.sqrt(25))</pre><p>Python also let’s you create a module yourself so you can reuse it whenever you want to. Simply save the code you want in a file with the file extension .py ✅</p><p>We simply call a module using the <strong>import</strong> statement.</p><p>When using a function from a module, we use the syntax: <strong>module_name.fumction_name()</strong>.</p><p>for example to use the function <strong>sqrt</strong> in the math module we say:</p><p><strong>math.sqrt(number)</strong></p><p>math — module name</p><p>sqrt — function_name</p><h4><strong>json</strong></h4><p>Python comes with a built-in <strong>json</strong> module. This gives you functions for working with JSON.</p><p><em>JSON stands for JavaScript Object Notation.</em></p><p>It is a way of storing and exchanging data in a format that both humans and programs can understand.</p><p>A JSON file looks a lot like a python dictionary. The first thing I asked myself was, why do we need json in python? why not just use a python dictionary? Well, turns out:</p><p><strong><em>A Python dict only exists inside Python’s memory, while it’s running.</em></strong></p><p>You can’t:<br>• Save a dict directly to a file<br>• Send a dict over the internet<br>• Store a dict in a database<br>• Pass a dict to a program written in another language (JavaScript, Java, etc.)</p><p>All of those things require plain text (or bytes) not a Python-specific object. JSON is a text format that almost every language can read and write, so it acts as a universal &quot;translator&quot; between systems.</p><pre>Function — What it does<br>json.dumps() — Python → JSON<br>json.loads() — JSON → Python<br>json.dump() —  Python → JSON file<br>json.load() — JSON file → Python</pre><h3><strong>Pip, Try…Except, User Input, VirtualEnv.</strong></h3><p>Think of pip as Python’s app installer 📦<br>When you install Python, you get many built-in tools. But sometimes you need a tool that doesn’t come with Python.<br>For example, you might want to work with data using pandas.<br>You can use pip to install it:</p><pre>pip install pandas</pre><p><strong>But what exactly is pip? </strong><br>pip is <strong>Python’s package installer</strong>.</p><p>A <em>package</em> is basically a collection of Python code that someone has created and made available for others to use.</p><p>For example:</p><pre>pandas       → data analysis<br>requests     → making HTTP requests<br>matplotlib   → creating visualizations<br>numpy        → numerical computing</pre><p>Install a package:</p><pre>pip install pandas</pre><p>Uninstall a package:</p><pre>pip uninstall pandas</pre><p>See installed packages:</p><pre>pip list</pre><p>Check information about a package:</p><pre>pip show pandas</pre><p>Upgrade a package:</p><pre>pip install --upgrade pandas</pre><h4><strong>Exception Handling.</strong></h4><p>Exception handling is like teaching your Python program what to do when something goes wrong, instead of letting the program suddenly crash. 🛡️</p><p><strong>First: What is an exception?</strong><br>An exception is an error that happens while your program is running.<br>For example:</p><pre>age = int(input(&quot;Enter your age: &quot;))</pre><p>if the user enters ‘Hello’, python cannot turn ‘Hello’ into an integer so you get:</p><pre>ValueError</pre><p>Without exception handling, the program stops.</p><p>Exception handling lets you say:<br>&quot;If this particular error happens, handle it this way.&quot;</p><p>The basic structure is:</p><blockquote>try:<br> # code that might cause an error</blockquote><blockquote>except:<br> # what to do if an error occurs.</blockquote><p>There is also <strong>else</strong></p><p>else runs only when no exception occurs.</p><p>And <strong>finally</strong><br>finally runs whether there was an error or not.</p><p>So the full structure can be:</p><p>try:<br> # risky code</p><p>except SomeError:<br> # handle error</p><p>else:<br> # runs if there was no error</p><p>finally:<br> # always runs</p><h4>User input.</h4><p>The input( ) function simply let’s us interact with the user.</p><pre>name=input(‘Enter your name: ’)</pre><p>The user types in their name and the code continues.</p><h4>Virtual Environment</h4><p>A virtual environment is like creating a separate workspace for a Python project, where that project’s packages and dependencies are kept isolated from other projects.</p><p>For example, imagine:</p><p>Project A → pandas 2.0</p><p>Project B → pandas 3.0</p><p>Without virtual environments, different projects can interfere with each other’s package versions.</p><p><strong>How to create a virtual environment:</strong></p><pre>python -m venv myenv</pre><p><strong>How to activate it</strong><br>Windows:</p><pre>myenv\Scripts\activate</pre><p>Mac/Linux:</p><pre>source myenv/bin/activate</pre><p>Then you can install packages:</p><pre>pip install pandas</pre><p>Those packages belong to that environment/project, rather than changing everything globally.</p><h4>Reading and Writing Files.</h4><p>Reading and writing files in Python simply means allowing your program to get information from a file or save information to a file.</p><p><strong>Opening a file.</strong><br>Python uses open():</p><pre>file = open(&quot;data.txt&quot;, &quot;r&quot;)</pre><p>The &quot;r&quot; means read, it let’s you read the file without editing it.<br>Common modes are:</p><pre>Mode — Meaning<br>&quot;r&quot;  — Read<br>&quot;w&quot; — Write (overwrites existing content)<br>&quot;a&quot; — Append (adds to existing content)<br>&quot;r+&quot; — Read and write</pre><p>A better way to handle File is using with. This automatically closes the file when you’re finished.</p><pre>with open(&quot;data.txt&quot;, &quot;r&quot;) as file:<br>content = file.read()</pre><p>Intro to SQL (Structured Query Language)</p><p>let’s say we have a table:</p><pre>id| name| age| department| salary<br>1| Ada| 24| IT| 100000<br>2| John| 30| Sales| 80000<br>3| Mary| 27| IT| 120000<br>4| Paul| 35| Sales| 90000</pre><p>1. <strong>SELECT</strong> — What do I want from the table?<br>Used to choose the columns you want to see.</p><pre>SELECT name, salary<br>FROM employees;</pre><p>Meaning:<br>Show me the name and salary of every employee.</p><p>To select everything:</p><pre>SELECT *<br>FROM employees;</pre><p>2. <strong>WHERE</strong> — Which rows do I want?<br>Used to filter data.</p><pre>SELECT *<br>FROM employees<br>WHERE department = &#39;IT’;</pre><p>Meaning:<br>&quot;Show me employees who work in IT.&quot;</p><p>You can also use comparisons:</p><pre>SELECT *<br>FROM employees<br>WHERE salary &gt; 90000;</pre><p>3. <strong>ORDER BY</strong> — allows you to arrange or sort the results. <br>Used to sort your results.</p><pre>SELECT *<br>FROM employees<br>ORDER BY salary;</pre><p>By default, it’s ascending.<br>For highest salary first:</p><pre>SELECT *<br>FROM employees<br>ORDER BY salary DESC;</pre><p>4. <strong>GROUP BY</strong> — allows you to group similar data.<br>Used when you want to create groups, often together with functions like COUNT(), AVG(), SUM(), etc.<br>For example:</p><pre>SELECT department, AVG(salary)<br>FROM employees<br>GROUP BY department;</pre><p>This gives you the average salary for each department.</p><p>5. <strong>JOIN</strong> — Allows you to combine tables.<br>The JOIN connects related information from different tables.<br>The most common types are:</p><p>- INNER JOIN → matching records from both tables<br>- LEFT JOIN → everything from the left table + matches from the right<br>- RIGHT JOIN → everything from the right table + matches from the left.</p><p>SQL is essentially about asking precise questions about your data.</p><h4><strong>Lesson from this week.</strong></h4><p>This week I understood modules and how useful they are in making programming simple and easy because you do not have to start from the scratch writing them.</p><p>This week is a lot less about just writing code and more about writing <strong>clean</strong> code that conforms with the standard.</p><h3>Key takeaways:</h3><p><strong>Module</strong> = a piece of Python code you can import.<br><strong>Package</strong> = a collection of Python modules.<br><strong>pip</strong> = a tool for installing packages from the Python ecosystem.</p><p>Thank you for reading up to this point. Please leave a like and comment if you found this article helpful. See you next week 👋. until then, Happy Coding ✨.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35121e2389d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 2: Understanding OOP, Inheritance, Polymorphism, Iterators and Scope.]]></title>
            <link>https://medium.com/@idogwuogechi/week-2-understanding-oop-inheritance-polymorphism-iterators-and-scope-ea95f316b674?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea95f316b674</guid>
            <category><![CDATA[polymorphism]]></category>
            <category><![CDATA[inheritance]]></category>
            <category><![CDATA[oop-concepts]]></category>
            <category><![CDATA[scopes]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 22:41:43 GMT</pubDate>
            <atom:updated>2026-09-27T12:54:52.517Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Laptop and notepad" src="https://cdn-images-1.medium.com/max/1024/0*Q4d7LoKGgRoupfvU" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Welcome to week two of my data science journey. If you missed week 1, you might want to check it out, because some of the concepts I’ll be discussing are built on it. That being said, let’s dive right in.</p><p>Week two of my data science journey exposed me to Object Oriented Programming (OOP), inheritance, polymorphism, iterators and scope. If these concepts are entirely new to you, don’t worry — I’ll break each one down in detail in this article.</p><h3>Object Oriented Programming (OOP)</h3><p>Let’s begin with OOP. If you are just starting out, this might be a lot to take in, but don’t worry, take deep breaths, we are going to do this together 😂.</p><p>Imagine you’re building an app to track drugs in a pharmacy. Without OOP, you might start like this:</p><pre>name1 = &quot;Paracetamol&quot;<br>dosage1 = 500<br>quantity1 = 30<br><br>name2 = &quot;Amoxicillin&quot;<br>dosage2 = 250<br>quantity2 = 20</pre><p><em>Sorry if can’t relate to this analogy, I am a Pharmacy student and this is the analogy I used to make it relatable. You can think of any other example you can relate to.</em></p><p>This already feels messy with just two drugs. Now imagine tracking 500. You’d need thousands of separate variables, and nothing tells Python that name1, dosage1, and quantity1 actually belong together as <em>one</em> drug.</p><p>This is the exact problem classes exist to solve. A class lets you define a blueprint — once — and then create as many objects from it as you need.</p><h3>Class vs Object</h3><p>A <strong>class</strong> is a blueprint.</p><p>An <strong>object</strong> is something created from that blueprint.</p><p>Think:</p><pre>class Patient:<br>    def __init__(self, name, age, medication):<br>        self.name = name<br>        self.age = age<br>        self.medication = medication<br><br>    def display_info(self):<br>        print(self.name, self.age, self.medication)</pre><p>Now creating a drug is clean:</p><pre>patient1 = Patient(&quot;John&quot;, 25, &quot;Paracetamol&quot;)<br>patient2 = Patient(&quot;Mary&quot;, 32, &quot;Amoxicillin&quot;)</pre><pre>patient1.display_info()<br>patient2.display_info()</pre><p>OOP becomes useful when your program has <strong>many related entities that have both data and behavior</strong>.</p><blockquote>I know this might sound abstract, no worries just follow along, it will sound less strange as we move further. You might want to take a close look at syntax in the above code because it outlines the basics of how a class is created.</blockquote><pre>| Concept      | Meaning                         |<br>| ------------ | ------------------------------- |<br>| `class`      | Creates a blueprint             |<br>| `__init__()` | Initializes an object           |<br>| `self`       | Refers to the current object    |<br>| method       | Function belonging to an object |</pre><h3>Why not just use a function?</h3><p>I asked myself this too. You technically <em>can</em> get away with functions and dictionaries for small scripts. But classes start earning their keep once:</p><ul><li>You have a lot of related data that always travels together</li><li>You have several pieces of behavior that only make sense <em>for</em> that data</li><li>Your project is going to grow</li></ul><p>let’s move to Inheritance.</p><h3>Inheritance</h3><blockquote>Inheritance allows you create subcategories inside the one main category which we have created in the class.</blockquote><p>Let’s say I’m building a small system to track vehicles. I start with a basic class:</p><pre>class Vehicle:<br>    def __init__(self, brand, model):<br>        self.brand = brand<br>        self.model = model<br><br>    def display_info(self):<br>        print(f&quot;Brand: {self.brand}, Model: {self.model}&quot;)</pre><p>Now, lets say we want to track cars. Cars have doors unlike motorcycles. We don’t need to copy the whole Vehicle class just to add a doors attribute. That would mean maintaining two nearly identical classes forever, and if we ever fix a bug in one, we’d have to remember to fix it in the other too.</p><p>This is exactly the problem inheritance solves:</p><pre>class Car(Vehicle):<br>    def __init__(self, brand, model, doors):<br>        super().__init__(brand, model)<br>        self.doors = doors<br><br>    def display_info(self):<br>        print(f&quot;Brand: {self.brand}, Model: {self.model}, Doors: {self.doors}&quot;)</pre><p>Car inherits everything Vehicle already has, it doesn’t need to redefine brand or model. super().__init__(brand, model) is how Car hands off the setup work it doesn’t need to handle itself, to the parent class.</p><p>An ElectricCar is a more specific kind of Car:</p><pre>class ElectricCar(Car):<br>    def __init__(self, brand, model, doors, battery_capacity):<br>        super().__init__(brand, model, doors)<br>        self.battery_capacity = battery_capacity<br><br>    def display_info(self):<br>        print(f&quot;Brand: {self.brand}, Model: {self.model}, Doors: {self.doors}, Battery: {self.battery_capacity}kWh&quot;)<br><br>tesla = ElectricCar(&quot;Tesla&quot;, &quot;Model 3&quot;, 4, 75)<br>tesla.display_info()</pre><p>As an output we will get:</p><pre>Brand: Tesla, Model: Model 3, Doors: 4, Battery: 75kWh</pre><p>Notice the chain here: ElectricCar → Car → Vehicle. Each class adds exactly one new layer of data, and each one passes along what it doesn&#39;t handle itself to the class above it. This is called <strong>multi-level inheritance</strong> — it&#39;s not limited to just one parent and one child.</p><h3>Polymorphism</h3><p>This sounds scary at first but the basic idea is surprisingly simple.</p><p><strong>Poly = many</strong></p><p><strong>Morphism = forms</strong></p><p>So:</p><blockquote>Polymorphism = one interface/operation, different behaviors.</blockquote><p>Imagine:</p><pre>class Dog:<br>    def speak(self):<br>        print(&quot;Woof&quot;)<br><br><br>class Cat:<br>    def speak(self):<br>        print(&quot;Meow&quot;)</pre><p>Both objects have:</p><pre>.speak()</pre><p>But they behave differently.</p><pre>dog = Dog()<br>cat = Cat()<br><br>dog.speak()<br>cat.speak()</pre><p>Output:</p><pre>Woof<br>Meow</pre><p>The same operation:</p><pre>.speak()</pre><p>produces different behavior depending on the object.</p><p>That’s polymorphism.</p><p>This becomes particularly useful in larger software systems where you want different objects to follow the same interface.</p><h3>Iterators</h3><p>Now let’s move away from OOP.</p><p>We’ve already used</p><pre>for number in [1, 2, 3, 4]:<br>    print(number)</pre><p><em>(if you haven’t please check my article on week one for better understanding)</em></p><p>You may have wondered:</p><blockquote><em>How does Python actually get the numbers one after another?</em></blockquote><p>That’s where <strong>iterators</strong> come in.</p><p>An iterator is an object that gives you values <strong>one at a time</strong>.</p><p>Python can use:</p><pre>iter()</pre><p>to create an iterator.</p><pre>numbers = [10, 20]<br>iterator = iter(numbers)</pre><p>Then:</p><pre>next(iterator)</pre><p>gives:</p><pre>10</pre><p>Again:</p><pre>next(iterator)</pre><p>gives:</p><pre>20</pre><p>After that, there are no more values, so Python raises</p><pre>StopIteration</pre><h3>Why do we need iterators? Why not stick to for loops?</h3><p>The important reason is:</p><blockquote><strong><em>They allow Python to process values one at a time rather than needing all values at once.</em></strong></blockquote><p>This becomes extremely useful with <strong>large datasets</strong>.</p><p>Imagine a file containing:</p><pre>10 million records</pre><p>You don’t necessarily want to load everything into memory simultaneously.</p><p>You can process data progressively.</p><h3>Scope</h3><p>Scope is probably the easiest concept conceptually.</p><p>It answers:</p><blockquote><strong><em>“Where can Python see this variable?”</em></strong></blockquote><p>Consider:</p><pre>x = 10<br><br>def test():<br>    print(x)<br><br>test()</pre><p>This works because x exists outside the function.</p><p>But:</p><pre>def test():<br>    x = 10<br><br>test()<br><br>print(x)</pre><p>doesn’t work.</p><p>Why?</p><p>Because x was created <strong>inside the function</strong>.</p><p>Its scope is local to that function.</p><h3>Local</h3><p>Inside the current function:</p><pre>def test():<br>    x = 10</pre><p>x is local.</p><h3>Global</h3><p>Outside functions</p><pre>x = 10<br><br>def test():<br>    print(x)</pre><p>x is global.</p><h3>Enclosing</h3><p>This happens with nested functions:</p><pre>def outer():<br>    x = 10<br><br>    def inner():<br>        print(x)</pre><p>x belongs to the enclosing function.</p><h3>Built-in</h3><p>Python’s built-in names:</p><pre>print()<br>len()<br>sum()<br>max()</pre><p>You don’t define these yourself.</p><p>I know this might be a lot to unpack 😂.</p><p>My Key takeaways:</p><blockquote><strong><em>OOP → How do I organize related data + functions?</em></strong><em><br> </em><strong><em>Inheritance → How do I reuse/extend an existing class?</em></strong><em><br> </em><strong><em>Polymorphism → How can different objects respond to the same operation in their own way?</em></strong><em><br> </em><strong><em>Iterators → How do I retrieve items one at a time?</em></strong><em><br> </em><strong><em>Scope → Where can a variable be accessed?</em></strong></blockquote><p>Truthfully, week two was a lot 🥲<em> (I barely survived 🤧)</em> . From understanding the concepts, to working on problems and building solutions, I felt like I had learned enough for one year 😂.</p><p>One thing I learnt: just understand the basics of the concepts, then work on solutions. The more you work on solutions, the more you solidify the concepts.</p><p>I hope you found this article insightful. Please do well to leave a like and a comment, they mean a lot. Thank you, and see you next week until then, Happy coding ✨.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea95f316b674" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My First Week as a Data Science Intern - Understanding the Basics.]]></title>
            <link>https://medium.com/@idogwuogechi/my-first-week-as-a-data-science-intern-understanding-the-basics-1d8700e6f37c?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d8700e6f37c</guid>
            <category><![CDATA[coding-for-beginners]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 22:59:32 GMT</pubDate>
            <atom:updated>2026-09-10T22:59:32.095Z</atom:updated>
            <content:encoded><![CDATA[<p>Data Science is an interesting and engaging field, but before you get into the interesting part, you will have to understand the basics. This article explores my first week&#39;s journey as a data science intern at Dataraflow.</p><figure><img alt="Coding" src="https://cdn-images-1.medium.com/max/1024/0*P0vVSOjABvvVRsTu" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=medium&amp;utm_medium=referral">Christopher Gower</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Building Blocks - The Fundamentals</h3><p>Every new language starts with vocabulary, and Python is no different. This week was about learning to understand and speak it, starting with the basics:</p><ul><li>Numbers, strings, and Booleans: show how Python stores and understands different kinds of data.</li><li>Lists, tuples, dictionaries, and sets : show the different ways to organize a collection of data, each with its own rules.</li><li>Comparison operators : `==`, `&gt;`, `&lt;`, and logical operators : show how Python checks and compares things.</li></ul><h3>Moving Past the Fundamentals to Solve Real-World Problems</h3><p>After learning the fundamentals — data types, comparison operators, if/elif/else statements, for loops, while loops, `range()`, functions, lambda expressions, map, and filter, etc., it was time for a little practice. If you are a beginner, you’re in luck, because I’ll be explaining how I used this concepts to solve problems like creating a program for a student grading system, a simple calculator, a shopping cart, and a guessing game.</p><h4>Task 1: Student Grades System</h4><p>The task was to write a program to accept marks for 5 subjects, calculate the average, and display the grade based on:</p><p>```<br>A: 80–100<br>B: 60–79<br>C: 40–59<br>F: &lt; 40<br>```</p><p>The solution:</p><pre>marks=[] #this creates an empty list to enter the marks<br>for i in range(1,6):<br>   mark = float(input(f&quot;Enter marks for subject {i}: &quot;))<br>   marks.append(mark)<br><br>average = sum(marks) /len(marks)<br><br>if average&gt;=80:<br>   grade=&quot;A&quot;<br>elif average &gt;= 60:<br>   grade=&quot;B&quot;<br>elif average &gt;= 40:<br>   grade = &quot;C&quot;<br>else:<br>   grade = &quot;F&quot;<br><br>print(f&quot;Average: {average}&quot;)<br>print(f&quot;Grade: {grade}&quot;)</pre><p>Why it works:<br>1. `marks = []` creates an empty list to store the marks<br>2. The for loop allows us to collect the user&#39;s input and append it to the empty list, looping through the range 1–5 (Python excludes the last number) to gather all 5 marks<br>3. The average is simply calculated as `sum(marks) / len(marks)`<br>4. The if/elif/else statements compare the average against each grade boundary and assign the matching grade<br>5. We print the average and grade as output</p><p>This block of code allows us to simply input students&#39; grades for 5 subjects and have the average calculated and the grade assigned.</p><h4>Task 2: Simple Calculator</h4><p>Build a calculator program that can perform addition, subtraction, multiplication, and division based on the user&#39;s input.</p><p>The solution:</p><pre>def calculator(a,b, operation):<br>    if operation == &quot;+&quot;:<br>        return a+b<br>    elif operation == &quot;-&quot;:<br>        return a-b<br>    elif operation == &quot;*&quot;:<br>        return a/b<br>    else:<br>        return&quot;Invalid operation&quot;<br><br>number1 = float(input(&quot;Enter the first number: &quot;))<br>number2 = float(input(&quot;Enter the second number: &quot;))<br>operation= input(&quot;Enter operation (+,*,-,/): &quot;)<br><br>output = calculator(number1,number2,operation)<br>print(f&#39;output: {output}&#39;)</pre><p>Why it works:<br>1. Defining the function with the parameters `(a, b, operation)` allows us to call on the function and perform operations with it as many times as needed<br>2. The if/elif/else statements allow us to perform multiple operations like addition, subtraction, multiplication, and division within the function<br>3. Assigning the user&#39;s inputs to variable names helps us use them as parameters when calling the function<br>4. The function performs the operation using the parameters supplied, and we get an output through the print statement</p><p>With this block of code we can perform operations like addition, subtraction, multiplication, and division.</p><h4>Task 3: Shopping Cart</h4><p>The task was to create a program where a user can add items to a shopping cart (a dictionary with item names and prices), then display the total cost.</p><p>The solution:</p><pre>cart = {}<br><br>while True:<br>    item = input(&quot;Enter item name(or &#39;done&#39; to finish): &quot;)<br>    if item == &quot;done&quot;:<br>        break<br>    price = float(input(f&quot;Enter price for {item}: &quot;))<br>    cart[item] = price<br><br>total = sum(cart.values())<br><br>print(&quot;\nYour cart: &quot;)<br>for item,price in cart.items():<br>    print(f&quot;{item}: #{price}&quot;)<br>print(f&quot;\nTotal cost: {total}&quot;)</pre><p>Why it works:<br>1. The empty dictionary named `cart` allows new inputs to be added<br>2. The `while True` condition creates a loop that prompts the user for the name of the item and its price and saves it to the cart; the loop continues until the user enters &quot;done,&quot; which breaks the loop<br>3. `sum(cart.values())` sums up the prices of the items<br>4. As output, we have the keys, which are the names of our items, together with their values, which are the prices</p><p>This block of code allows us to quickly see items purchased and their total.</p><h4>Task 4: Guessing Game</h4><p>The task was to write a program where the computer randomly selects a number between 1–20 that the user must guess. Give hints if the guess is too high or too low.</p><p>The solution:</p><pre>import random<br><br>number = random.randint(1,20)<br>guess = None <br><br>while guess != number:  #this creates a condition that once the guessed number is not equal to the secret number,the loop continues.<br>  guess = int(input(&quot;Guess a number between 1-20: &quot;))<br>  if guess &lt; number:<br>    print(&quot;Too low&quot;)<br>  elif guess&gt;number:<br>    print(&#39;Too high&#39;)<br>  else:<br>    print(&quot;You guessed the number right&quot;)</pre><p>Why it works:<br>1. `import random` brings in a built-in module in Python that allows the computer to select a number at random (in this case, from 1–20)<br>2. The `while guess != number` loop keeps running the if/elif/else statements as long as the guess doesn’t equal the number, and breaks the loop once the guess equals the number.</p><p>This block of code allows us to create a guessing game where users input numbers and keep guessing until they get the actual number.</p><p>The exercise that got me stuck? That was task 5 😩. I felt like it was a step above the fundamentals I had learnt, and I did not know how to go about it at first.</p><p>The task was to write a program that accepts a list of student names from the user, saves them in a text file, and then reads and displays them.</p><p>The solution:</p><pre>students = []<br>while True:<br>    name = input(&quot;Enter a stdent name (or done to finish)&quot;)<br>    if name == &quot;done&quot;:<br>        break<br>    students.append(name)<br><br>with open(&quot;students.txt&quot;, &quot;w&quot;) as file:<br>    for name in students:<br>        file.write(name + &quot;\n&quot;)<br><br>with open (&quot;students.txt&quot;, &quot;r&quot;) as file:<br>    print(&quot;\nStudents from file: &quot;)<br>    for line in file:<br>        print(line.strip())</pre><p>Why it works:<br>1. The `with open()` pattern is the best practice for handling files in Python. It acts as an automatic cleanup crew: even if an error happens while writing, it ensures the file is closed properly, so your data isn&#39;t corrupted.<br>2. Writing data (&quot;w&quot; mode): the program uses `&quot;w&quot;` to open the file. Every time you enter a valid name, `.write(name + &quot;\n&quot;)` appends an invisible line break to push the next entry down to a new line in the text file. `&quot;r&quot;` mode reopens it to read.<br>3. `.strip()` removes the extra newline character when printing each name back.</p><p>This week&#39;s learning showed me how powerful the fundamentals can be in solving complex problems in data science, and how important it is to understand the basics before moving on to even more complex tasks. As it will create a solid foundation upon which you can write and execute even more powerful code.</p><p>Note: There is more than one way to solve these exercises, and your solution may differ slightly from mine. That’s okay, as long as it gives the required output.</p><p>That’s it for week one. If this article helped you, or if you have any comments or suggestions, please leave them in the comments , I’d really love to hear from you. I’m also looking forward to connecting with you 😊.</p><p>See you next week 👋.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d8700e6f37c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Found My Path in Tech After Quitting So Many Times.]]></title>
            <link>https://medium.com/@idogwuogechi/how-i-found-my-path-in-tech-after-quitting-so-many-times-94b600451403?source=rss-becda74f8d29------2</link>
            <guid isPermaLink="false">https://medium.com/p/94b600451403</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Idogwu ogechukwu Luciana]]></dc:creator>
            <pubDate>Sat, 16 Aug 2025 16:30:41 GMT</pubDate>
            <atom:updated>2025-08-16T16:30:41.313Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The number of times I have written and scrapped my bucket list is the same as the number of times Edison used to perfect the light bulb</em>.</p><figure><img alt="Sunlight " src="https://cdn-images-1.medium.com/max/1024/0*abyes1Yd6e2le3JE" /><figcaption>Photo by <a href="https://unsplash.com/@ameenfahmy?utm_source=medium&amp;utm_medium=referral">ameenfahmy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is the sad reality of my journey to becoming the best version of myself. As I sat yesterday staring at my bucket list, those were the words that rang through my head, and for a moment my heart ached for all that would have been, if only…</p><p>While writing this, I realized just how much I have tried to discover myself through a series of trials and errors, and I smiled because if my life were some experimental lab, it would have exploded due to certain unfit experimental trials 😂.</p><p>I have always loved the tech world, so it has always been a question of where I fit in.</p><p>The first was content creation. I thought I wasn’t so bad at writing, so it wouldn’t hurt to give it a shot. But that ended as quickly as it began.</p><p>And then I picked up graphics design, and after I got a hang of the basics and created a few good flyers, I decided to go into UI/UX design. But somewhere along the way, I lost interest and quit. Same thing happened with web design, and then software development, and a few others. I know what you’re thinking, and I don’t blame you for judging me (if you are). I myself judged my incompetence to perfect a skill, so that’s fine.</p><figure><img alt="Searching…" src="https://cdn-images-1.medium.com/max/1024/0*iUtlGxS6k0i8kzhl" /><figcaption>Photo by <a href="https://unsplash.com/@wflwong?utm_source=medium&amp;utm_medium=referral">Warren</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Well early this year, I ventured into data analytics and guess what? I...</p><p>I’m still at it! 😂 To be honest, I did quit a few times. I mean, being a full-time pharmacy student and a data analyst was tougher than I expected. Some days, there’s this surge of adrenaline, this spike of motivation, and this deep resolve to keep at it. Other days, there’s just tiredness and the urge to run to the next tech skill.</p><p>Well, I can’t because I have my resonance with data. I’ve had enough explorations to know that data analytics is the best tech career path for me, and that’s what trial and error teaches us, that’s what failure teaches us. It shows us the way forward. It gives us certainty. It allows us to explore our prospects and choose our best fit.</p><p>So it’s okay not to figure it all out from the start, it’s okay to test the waters and decide if that’s really what you want to do. I guess that was what Edison implied when he said, <em>&quot;I have not failed 1,000 times. I have successfully discovered 1,000 ways that do not work.&quot;</em></p><p>Your trials and errors, your failures, they all add up to give a whole new experience, a different perspective, an edge. My writing skills from content creation are what kept you hooked to this article, don’t you think? 😂</p><p>And no, this is not just some random cliché motivation to keep you going. This is my journey to becoming the best version of myself. And I hope you find a reason to reach out for that version of yourself too. I’m rooting for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F9LNpSCMLD9or3Aw" /><figcaption>Photo by <a href="https://unsplash.com/@theshuttervision?utm_source=medium&amp;utm_medium=referral">Jonathan Cooper</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Feel free to follow me on LinkedIn <a href="https://www.linkedin.com/in/lucianaidogwu?utm_source=share&amp;utm_campaign=share_via&amp;utm_content=profile&amp;utm_medium=android_app">here</a> where I share insightful contents to aid your growth and learning journey. See you in my next article until then keep exploring 😉.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94b600451403" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>