Name Cannot be Blank💀

Let's be honest about something most people won't admit you've probably spent hours watching coding tutorials, nodding along, typing exactly what the instructor types, and at the end you felt... nothing. Maybe a bit accomplished for finishing, but also kind of empty. Here's why:you didn't learn anything. You just proved you can copy. I know that sounds harsh, but think about it. When you follow along step-by-step, your brain is on autopilot. You're not making decisions. You're not problem-solving. You're basically a human Ctrl+C, Ctrl+V machine. And the second you close that tutorial, everything is gone. All of it. Real learning happens in the uncomfortable middle ground where you're trying to remember what to do next, and you can't. That moment when you think, wait, why did they use a LEFT JOIN here instead of an INNER JOIN?" — that's when your brain actually wakes up. Here's how I learn, and it should work for you, too. After you finish a tutorial, close it. Don't rewatch it. Don't peek at the code. Instead, grab a different dataset — it could be from Kaggle, could be your own data, doesn't matter — and try to solve a similar problem from memory. You're going to fail. You're going to forget the steps. You're going to write code that doesn't work. Perfect. That's exactly where learning lives. When you get stuck, then go back and check. But only after you've tried. Because that struggle — that annoying, frustrating feeling is your brain actually building the skill. You'll be slow. You'll make mistakes. You'll wonder if you learned anything at all from that tutorial. But here's what's happening: you're forcing your brain to retrieve information instead of just recognizing it. Retrieval is what builds real memory. If this changes how you think about learning, follow me for more honest takes.

Femi: This IF Function in Excel… how does it really work? Me: Excel’s IF Funtion is basically like a judge sitting in your cell. You give it a question, it looks at the situation, and it decides what answer to return. You’re not doing magic. You’re just saying, “Excel, check this thing. If it’s true, say this. If it’s not, say that.” That’s the whole idea. Say you want to check if the number in A1 is greater than 5. If it is, Excel should say “YES.” If it’s not, it should say “NO.” Here’s the formula: `=IF(A1>5,"YES","NO")` Nothing complicated. It’s built on three simple parts: 1. What do you want Excel to check 2. What to show if the condition is true 3. What to show if it’s false Think of it like asking a friend, is the weather hot? If they say yes, you wear a T-shirt. If they say no, you grab a hoodie. You set those up, Excel does the rest. Across hundreds of rows if you want. And here's where it gets good—once you get the basic idea, you can build bigger logic. String multiple IFs together. Nest them. Layer them until your spreadsheet starts doing the thinking for you. Want more beginner-friendly breakdowns? Stick around.

lost in the queries.

Day 1 of learning SQL: This is easy, just SELECT and FROM. Day 3: INNER JOIN, LEFT JOIN, RIGHT JOIN. Day 5: Staring at screen wondering if you're still learning SQL or ancient Greek Have you been there before? 😃

How would you rate yourself in Microsoft Excel ? A. Master B. Professional C. Intermediate D. Beginner Be honestly—No shame in being real.

Spotify pays attention to when you skip a song. Because that moment tells them more about your taste than anything else. They found that most people decide if they like a song within the first five seconds. That’s a small action, but it carries meaning. Your attention, your hesitation, your quick decisions, your patterns —those are all data points. They’re recorded, compared, analyzed and studied to understand what you prefer and why. This is where data analysis shows up in everyday life. Someone is responsible for: • Collecting those skip events • Cleaning the data • Spotting patterns across millions of listeners • Turning that into decisions and actionable insights. So when people ask “What does a data analyst actually do?” Here’s the answer: They look into tiny behaviors, study and analyze them , trace the pattern, and explain what they mean to make decisions Data isn’t just numbers. It’s people making tiny choices, over and over, without realizing it. And our job is to understand those choices..

September 9th, 1947. Grace Hopper's computer stops working. Her team can't figure out why. They open it up and find a moth stuck inside the machine Grace tapes it into her log book and writes: "First actual case of bug being found." That's where the word "bug" comes from. An actual insect breaking a computer. Fast forward to Today ,when your code doesn't work, you're debugging. You're looking for the problem, just like Grace did. Except now, the bugs aren't physical. They're mistakes in the code. Typos. Logic errors. Things you can't see or touch. But we still call them bugs because of that one moth in 1947.

you ever follow a tutorial word for word — same code, same dataset, same everything — theirs works perfectly and yours just... doesn't like, WHERE did i go wrong. we're literally typing the same things

$28.2 Million. That's how much money was at risk when I opened this dataset. I wasn't expecting it. I thought I was just building another loan dashboard. Clean the data, add some charts, and call it a day. But then I saw it—buried in the numbers—a quiet crisis hiding in plain sight. Here's what happened A bank was processing thousands of loan applications every month. On paper, everything looked fine. Growth was up. Funding was strong. The executive summary would've made anyone smile. But I created a helper column. Just one. To separate Performing Loans from Non-Performing Loans. And that's when the story changed. 13.8% of loans weren't being repaid. 5,300 borrowers. $65.5 million funded. Only $37.3 million recovered. The rest? Lost to defaults and charge-offs. Almost $30 million in risk that no one was actively watching. So I didn't stop at the KPIs. I went deeper: ✅ Built MTD/MOM comparison logic to track momentum ✅ Used Pivot Tables to isolate problem areas ✅ Added slicers so stakeholders could filter by loan purpose and grade ✅ Created a two-page navigation system—one for performance, one for risk The result? A dashboard that didn't just report numbers. It told a story. More importantly, it gave leadership a path forward What happened after I discovered this? The full story is in here → shorturl.at/ijZyx