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.