FC Barcelona Sierra Leone

08/30/2026

𝗔𝗜 𝗵𝗮𝘀 𝗺𝗮𝗱𝗲 𝗶𝘁 𝗲𝗮𝘀𝗶𝗲𝗿 𝘁𝗵𝗮𝗻 𝗲𝘃𝗲𝗿 𝘁𝗼 𝘄𝗿𝗶𝘁𝗲 𝗰𝗼𝗱𝗲.

Paste an error.

Describe what you want.

Seconds later, you have Python or SQL that looks ready to run.

But there is a skill becoming even more important:

Debugging.

Because AI-generated code can:

• Run without errors but produce the wrong result
• Reference the wrong column
• Use an inappropriate join
• Introduce data leakage
• Handle NULLs incorrectly
• Make assumptions you never specified
• Use outdated methods or libraries

So when AI gives me code, I don’t only ask:

“Does it run?”

I also ask:

1️⃣ Do I understand what every important step is doing?

2️⃣ What assumptions did AI make?

3️⃣ Are the inputs and data types what the code expects?

4️⃣ Can I test the logic on a few records manually?

5️⃣ Do the row counts and distributions still make sense?

6️⃣ Does the output answer the actual business question?

This is why I don’t think learning Python, SQL, or statistics has become less important because of AI.

I think the opposite has happened.

🤖 AI reduces the value of simply memorizing syntax.

But it increases the value of:

• Problem solving
• Debugging
• Validation
• Critical thinking
• Business understanding

𝗬𝗼𝘂 𝗱𝗼𝗻’𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗰𝗼𝗺𝗽𝗲𝘁𝗲 𝘄𝗶𝘁𝗵 𝗔𝗜 𝗮𝘁 𝘄𝗿𝗶𝘁𝗶𝗻𝗴 𝗰𝗼𝗱𝗲.

You need to become good at knowing when the code is wrong.

💬 Has AI made you better at debugging—or more dependent on generated code?

📌 Save this for your next AI-assisted project.

🌐 More practical tutorials and cheat sheets:

EverydayDataScience.com

Follow AI & Data With Ibrahim for practical lessons on Python, SQL, Data Analytics, Machine Learning, Data Engineering, and AI.

Learn • Build • Share • Inspire

08/27/2026

𝗔 𝗺𝗮𝗰𝗵𝗶𝗻𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗺𝗼𝗱𝗲𝗹 𝗰𝗮𝗻 𝗽𝗲𝗿𝗳𝗼𝗿𝗺 𝗴𝗿𝗲𝗮𝘁 𝗶𝗻 𝘁𝗵𝗲 𝗻𝗼𝘁𝗲𝗯𝗼𝗼𝗸 𝗮𝗻𝗱 𝘀𝘁𝗶𝗹𝗹 𝗳𝗮𝗶𝗹 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝘄𝗼𝗿𝗹𝗱.

That is one of the biggest differences between building a model and building a reliable machine-learning system.

You can have:

• Strong validation scores
• Clean training data
• Good feature engineering
• A well-tuned model

And still run into problems after deployment.

Why?

Because production changes the game.

Here are 5 reasons a good model can fail after launch:

1️⃣ 𝗗𝗮𝘁𝗮 𝗱𝗿𝗶𝗳𝘁
The data your model sees today may not look like the data it was trained on.

Customer behavior changes.

Markets change.

Products change.

Processes change.

2️⃣ 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝗱𝗿𝗶𝗳𝘁
The relationship between your inputs and target can change over time.

A pattern that predicted churn six months ago may not work the same way today.

3️⃣ 𝗕𝗮𝗱 𝗼𝗿 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝗶𝗻𝗽𝘂𝘁𝘀
APIs fail.

Columns change.

Values go missing.

Categories appear that the model has never seen before.

4️⃣ 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗹𝗼𝗼𝗽𝘀
Your model can influence the behavior it is trying to predict.

For example, if a recommendation system keeps showing the same kind of content, future user behavior may partly reflect the model’s own decisions.

5️⃣ 𝗡𝗼 𝗺𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴
If nobody is watching the model after deployment, performance can quietly degrade for weeks or months.

That is why production ML needs more than:

model.fit()

and

model.predict()

You also need to monitor:

• Input distributions
• Prediction distributions
• Performance metrics
• Missing values
• Latency
• Errors
• Business outcomes

🤖 𝗪𝗵𝗮𝘁 𝗮𝗯𝗼𝘂𝘁 𝗔𝗜?

AI can help you write the pipeline, generate monitoring code, detect anomalies, and summarize performance.

But someone still has to decide:

• What should be monitored?
• When is a change significant?
• When should the model be retrained?
• When should we fall back to a simpler rule?
• Is the model still helping the business?

𝗧𝗿𝗮𝗶𝗻𝗶𝗻𝗴 𝗮 𝗺𝗼𝗱𝗲𝗹 𝗶𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲 𝗳𝗶𝗻𝗶𝘀𝗵 𝗹𝗶𝗻𝗲.

It is the beginning of the model’s real test.

💬 Which production ML challenge do you think is hardest: drift, monitoring, feedback loops, or data quality?

📌 Save this for your next machine-learning project.

🌐 More practical tutorials and cheat sheets:

EverydayDataScience.com

Follow AI & Data With Ibrahim for practical lessons on Python, SQL, Data Analytics, Machine Learning, Data Engineering, and AI.

Learn • Build • Share • Inspire

Practical AI, machine learning, and data science for people who build, with a focus on agentic systems and applied AI in Africa. Written by practitioners.

08/22/2026

𝗢𝗻𝗲 𝗦𝗤𝗟 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗰𝗮𝗻 𝗾𝘂𝗶𝗲𝘁𝗹𝘆 𝗿𝗲𝗺𝗼𝘃𝗲 𝗵𝘂𝗻𝗱𝗿𝗲𝗱𝘀 𝗼𝗳 𝗿𝗼𝘄𝘀 𝗳𝗿𝗼𝗺 𝘆𝗼𝘂𝗿 𝗮𝗻𝗮𝗹𝘆𝘀𝗶𝘀.

And sometimes, you will not even notice.

Imagine you have:

1,000 customers

and you join them to an orders table.

If you use:

INNER JOIN

you only keep customers who have matching orders.

So if 180 customers have never placed an order…

they disappear.

Your result now has 820 customers.

That may be exactly what you want.

Or it may completely change the business question.

This is why, during exploratory analysis, I often prefer to start with a:

LEFT JOIN

It keeps every customer from the left table—even when there is no matching order.

Then I can ask:

• Who has never ordered?
• Which records failed to match?
• Are the join keys clean?
• Are we losing important rows?
• Is “no match” itself an insight?

𝗧𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗶𝘀 𝘀𝗶𝗺𝗽𝗹𝗲:

INNER JOIN → Keep only matches.

LEFT JOIN → Keep everything from the left + whatever matches on the right.

Neither is automatically better.

The correct join depends on the question you are answering.

Before accepting the result of any join, I like to check:

1️⃣ Row count before the join
2️⃣ Row count after the join
3️⃣ Number of unmatched records
4️⃣ Whether the join created duplicates
5️⃣ Whether the join key is actually unique

🤖 𝗔𝗻𝗱 𝘄𝗵𝗮𝘁 𝗮𝗯𝗼𝘂𝘁 𝗔𝗜?

AI can write your SQL join in seconds.

But if you simply say:

“Join these two tables”

it may produce perfectly valid SQL that answers the wrong business question.

You still need to understand:

What should happen to records that do not match?

That is not a syntax question.

That is an analysis question.

𝗚𝗼𝗼𝗱 𝗦𝗤𝗟 𝗶𝘀 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗮𝗯𝗼𝘂𝘁 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝗾𝘂𝗲𝗿𝘆 𝘁𝗼 𝗿𝘂𝗻.

𝗜𝘁 𝗶𝘀 𝗮𝗯𝗼𝘂𝘁 𝗸𝗻𝗼𝘄𝗶𝗻𝗴 𝘄𝗵𝗶𝗰𝗵 𝗿𝗼𝘄𝘀 𝘆𝗼𝘂 𝗮𝗿𝗲 𝗸𝗲𝗲𝗽𝗶𝗻𝗴 — 𝗮𝗻𝗱 𝘄𝗵𝗶𝗰𝗵 𝗼𝗻𝗲𝘀 𝘆𝗼𝘂 𝗮𝗿𝗲 𝗹𝗼𝘀𝗶𝗻𝗴.

💬 Which do you use more during analysis: INNER JOIN or LEFT JOIN?

📌 Save this for your next SQL project.

🌐 More practical tutorials and cheat sheets:

EverydayDataScience.com

Follow AI & Data With Ibrahim for practical lessons on SQL, Python, Data Analytics, Data Engineering, Machine Learning, and AI.

Learn • Build • Share • Inspire

08/21/2026

𝗠𝗼𝗿𝗲 𝗰𝗵𝗮𝗿𝘁𝘀 𝗱𝗼 𝗻𝗼𝘁 𝗺𝗮𝗸𝗲 𝗮 𝗯𝗲𝘁𝘁𝗲𝗿 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱.

In fact, they often make it worse.

One of the easiest mistakes to make in Power BI, Tableau, or Excel is trying to show everything.

Every KPI.

Every chart.

Every slicer.

Every possible breakdown.

The result?

A dashboard that looks busy but makes the decision harder.

𝗔 𝗴𝗼𝗼𝗱 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝘀𝗵𝗼𝘂𝗹𝗱 𝗮𝗻𝘀𝘄𝗲𝗿 𝗮 𝗳𝗲𝘄 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀 𝗾𝘂𝗶𝗰𝗸𝗹𝘆.

Before adding another visual, ask:

1️⃣ 𝗪𝗵𝗮𝘁 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗱𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝗰𝗵𝗮𝗿𝘁 𝘀𝘂𝗽𝗽𝗼𝗿𝘁?

If the answer is “none,” it probably does not belong there.

2️⃣ 𝗗𝗼𝗲𝘀 𝗶𝘁 𝗮𝗱𝗱 𝗻𝗲𝘄 𝗶𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻?

Three visuals telling the same story are usually unnecessary.

3️⃣ 𝗖𝗮𝗻 𝘁𝗵𝗲 𝘂𝘀𝗲𝗿 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗶𝘁 𝗶𝗻 𝟱 𝘀𝗲𝗰𝗼𝗻𝗱𝘀?

If not, simplify it.

4️⃣ 𝗜𝘀 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗶𝗻𝘀𝗶𝗴𝗵𝘁 𝗼𝗯𝘃𝗶𝗼𝘂𝘀?

Your audience should not have to hunt for the point.

5️⃣ 𝗖𝗼𝘂𝗹𝗱 𝗼𝗻𝗲 𝗯𝗲𝘁𝘁𝗲𝗿 𝘃𝗶𝘀𝘂𝗮𝗹 𝗿𝗲𝗽𝗹𝗮𝗰𝗲 𝘁𝘄𝗼 𝗼𝗿 𝘁𝗵𝗿𝗲𝗲 𝘄𝗲𝗮𝗸𝗲𝗿 𝗼𝗻𝗲𝘀?

Often, yes.

🤖 𝗔𝗜 𝗰𝗮𝗻 𝗯𝘂𝗶𝗹𝗱 𝘃𝗶𝘀𝘂𝗮𝗹𝘀 𝗳𝗮𝘀𝘁.

But speed can make it easier to overbuild.

AI can suggest charts, layouts, and KPIs.

You still need to decide what actually deserves attention.

𝗧𝗵𝗲 𝗯𝗲𝘀𝘁 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝗶𝘀 𝗻𝗼𝘁 𝘁𝗵𝗲 𝗼𝗻𝗲 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗰𝗵𝗮𝗿𝘁𝘀.

It is the one that helps someone understand the situation and make a decision faster.

💬 What is the most common dashboard mistake you see?

📌 Save this before building your next dashboard.

🌐 More practical tutorials and cheat sheets:

EverydayDataScience.com

Follow AI & Data With Ibrahim for practical lessons on Power BI, Excel, SQL, Python, Data Analytics, Machine Learning, and AI.

Learn • Build • Share • Inspire

08/15/2026

🚀 **AI can clean your data.**

But can you tell if it cleaned it correctly?

That's becoming one of the most valuable skills in data analytics.

Today, tools like ChatGPT, Claude, and GitHub Copilot can generate Pandas code in seconds.

I use AI every day.

But here's the reality:

**AI is only as good as the person reviewing its output.**

Imagine AI gives you code to fill missing values.

Do you know:

- Should the missing values be removed or filled?
- Is the median a better choice than the mean?
- Are those duplicates actually duplicates?
- Is that outlier an error or a legitimate business event?
- Did the cleaning introduce bias into your analysis?

These are decisions AI **cannot** make for you without context.

That's why every Data Analyst needs strong data cleaning fundamentals.

Master these 10 tasks and you'll be able to:

✅ Handle missing values correctly

✅ Remove duplicate records

✅ Fix incorrect data types

✅ Standardize inconsistent text

✅ Detect outliers

✅ Validate your data

Because here's the truth:

**Garbage In = Garbage Out.**

Even the most advanced AI model can't produce reliable insights from poor-quality data.

Clean data is the foundation of accurate dashboards, trustworthy reports, and successful machine learning models.

The goal isn't to avoid AI.

The goal is to **use AI with understanding.**

When you know the fundamentals, AI becomes your assistant—not your replacement.

💬 **Which data cleaning task do you find the most challenging?**

👇 **Save this post.** It's a checklist you'll use throughout your data analytics journey.

📚 Get more free Data Analytics cheat sheets, tutorials, and career resources:

**https://everydaydatascience.com**

Follow **AI & Data With Ibrahim** for practical lessons on SQL, Python, Data Analytics, Data Engineering, Machine Learning, and AI.

**Learn • Build • Share • Inspire**

08/11/2026

What if your business logo could transform into your actual product? 👀

In this video, I uploaded the Rolex logo to Gemini and transformed it seamlessly into a luxury wristwatch—without using complicated animation software.

You can try this with your own logo and turn it into shoes, perfume, clothing, food packaging, electronics, or almost any product.

Comment LOGO below, and I’ll send you the complete prompt and instructions for free. 🔥

08/09/2026

𝗔 𝗺𝗮𝗰𝗵𝗶𝗻𝗲 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗺𝗼𝗱𝗲𝗹 𝗰𝗮𝗻 𝗯𝗲 𝟵𝟱% 𝗮𝗰𝗰𝘂𝗿𝗮𝘁𝗲 𝗮𝗻𝗱 𝘀𝘁𝗶𝗹𝗹 𝗯𝗲 𝗮 𝗯𝗮𝗱 𝗺𝗼𝗱𝗲𝗹.

Imagine you’re predicting fraud.

Out of 1,000 transactions:

• 950 are legitimate
• 50 are fraudulent

Now imagine your model predicts:

“Legitimate” for every single transaction.

Its accuracy?

95%.

Looks impressive.

But it detected zero fraud cases.

That is why accuracy alone can be misleading.

Before celebrating a model, ask:

1️⃣ 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗰𝗹𝗮𝘀𝘀 𝗯𝗮𝗹𝗮𝗻𝗰𝗲?
Is one outcome much more common than the other?

2️⃣ 𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝗽𝗿𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝘁𝗲𝗹𝗹 𝗺𝗲?
When the model predicts positive, how often is it correct?

3️⃣ 𝗪𝗵𝗮𝘁 𝗱𝗼𝗲𝘀 𝗿𝗲𝗰𝗮𝗹𝗹 𝘁𝗲𝗹𝗹 𝗺𝗲?
How many of the actual positive cases did we catch?

4️⃣ 𝗪𝗵𝗮𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗰𝗼𝘀𝘁 𝗼𝗳 𝗮 𝗳𝗮𝗹𝘀𝗲 𝗽𝗼𝘀𝗶𝘁𝗶𝘃𝗲 𝗼𝗿 𝗳𝗮𝗹𝘀𝗲 𝗻𝗲𝗴𝗮𝘁𝗶𝘃𝗲?
In healthcare, fraud, lending, or cybersecurity, the consequences can be very different.

5️⃣ 𝗗𝗼𝗲𝘀 𝘁𝗵𝗲 𝗺𝗲𝘁𝗿𝗶𝗰 𝗺𝗮𝘁𝗰𝗵 𝘁𝗵𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗽𝗿𝗼𝗯𝗹𝗲𝗺?
The “best” metric depends on what decision the model supports.

🤖 𝗪𝗵𝗮𝘁 𝗮𝗯𝗼𝘂𝘁 𝗔𝗜?

AI can train the model.

AI can calculate accuracy, precision, recall, F1-score, and ROC-AUC.

AI can even recommend a model.

But you still need to decide which mistake matters most to the business.

That requires context and judgment.

𝗗𝗼𝗻’𝘁 𝗮𝘀𝗸 𝗼𝗻𝗹𝘆:

“How accurate is the model?”

Ask:

“Is the model good at the thing we actually care about?”

💬 Which metric do you look at first when evaluating a classification model?

📌 Save this for your next machine learning project.

🌐 More practical tutorials and cheat sheets:
EverydayDataScience.com

Follow AI & Data With Ibrahim for practical lessons on Python, SQL, Data Analytics, Machine Learning, Data Engineering, and AI.

Learn • Build • Share • Inspire

08/09/2026

df.describe() is not Data Analysis
science

08/08/2026

🚨 I’m Going Live: Healthcare Data Analytics for Beginners

I’m starting a new Healthcare Analytics Series where I’ll be learning, building, and sharing the entire process publicly.

In Episode 1, we’ll break down:

• What healthcare analytics actually means
• What healthcare claims data is
• Why claims data matters
• How patients, providers, diagnoses, procedures, payers, and costs connect
• Why SQL and data engineering are so important in healthcare
• The production-quality healthcare analytics project we’re building from scratch

This is designed for data analysts, data scientists, students, and anyone interested in breaking into healthcare analytics.

No complicated coding in Episode 1 — we’re starting with the fundamentals so everything we build afterward actually makes sense.

🎥 Join me LIVE on YouTube:
https://www.youtube.com/live/aYxw4qs6IDw?is=pjquYoabECmGtCPe

🔔 Set your reminder and come learn with me.

AI & Data With Ibrahim
Learn • Build • Share • Inspire

Every healthcare analyst job posting asks for claims data experienc...

08/08/2026

Dog.describe () is not Data Analysis