Pinned Tweet
Learning data analytics in public has taught me something deeper than Excel or SQL. 馃搳
You can start from somewhere completely different and still build something meaningful.
I studied Animal Science.
I taught in classrooms.
I worked in customer service and sales.
Now, I'm learning data analytics.
And honestly, starting over isn't always easy.
There are days when you feel behind.
Days when you wonder if you're learning fast enough.
Days when the people around you seem miles ahead.
But I'm learning that progress doesn't require you to have everything figured out.
It starts with asking better questions.
1. Start with the question, not the tool.
Before opening Excel, ask:
What decision will this analysis help someone make?
2. Understand your data.
Where did it come from?
What does it leave out?
Can you trust it?
3. Learn the fundamentals.
Tools will change.
AI will get better.
But the ability to think clearly will always matter.
4. Learn to communicate.
Finding an insight is one thing.
Explaining it clearly enough for someone to act on it is another.
5. Build by solving real problems.
Don't just learn formulas.
Don't just watch tutorials.
Take a messy problem.
Work through it.
Make mistakes.
Figure it out.
Share what you learned.
AI can write a formula or SQL query in seconds.
But knowing what to ask, what to investigate, and what the answer actually means is the skill I'm building.
I'm Obinna.
I'm learning data analytics in public, one real problem at a time.
If you're learning a new skill, changing careers, or starting over too, you're not alone.
We're building from where we are.
What are you currently learning that could change your career?
The first thing I do before touching a new file is copy it. Rename the copy, leave the original alone.
Half of getting better at Excel is being willing to break something, and you're only willing when you know you can get it back.
9
Excel is not a spreadsheet, it's a question-asking tool. SUM asks one question. SUMIF asks a better one. Most people stop at SUM, accept the total, and never find out what's inside it.
17
The only thing that has moved anything for me this month is one finished piece with a real number in it. Not threads, not tips, not posting more. Take one dataset, find one thing that's wrong, write it up. That's the whole strategy.
I still get the syntax wrong the first time. Every time. What changed is that I now open the file anyway instead of waiting to feel ready. If you're starting late, the gap isn't talent, it's reps. Open the file tonight.
1
33
A blank cell is not a zero. SUM ignores it. AVERAGE ignores it. But your percentage of the total quietly changes, and your row count stops matching your answer. Before you trust a number, find the blanks. Filter for empty, count them, then decide what they actually mean
15
1,871 order lines in the Superstore file lost money. That's 18.7% of the table.
Average loss was about 83 each. That's small enough that no single row looks like a problem.
Before you trust a profit total, run COUNTIF on the profit column for anything below zero.
1
13
1,448 followers on LinkedIn, and the follower count isn't what brings in clients for my profile work.
The posts get people to click through. The profile is built to catch them when they land.
Funnel first. Volume second.
1
2
39
I've been calling it waiting. Some days it's just wasting.
Applications are out and nothing is paying in the meantime. I'm 34 and I want a family.
One day my own work will pay enough that I stop working for other people. Today I need a job.
1
26
Excel first, then SQL. You can spend a year in Excel and still not know what to check in a number, and SQL will just let you query the wrong thing faster.
1
32
Split the Superstore profit by discount and the whole story changed.
Full-price orders: 320,987.60 profit.
Discounted orders: -34,590.60.
I went in looking for a rounding error. It was a pricing problem.
1
32
One of my students told me he fishes before school because it pays his fees.
I've never been able to teach that boy the same way again. Every lesson plan since has had to answer a question he never asked out loud: what is this actually for.
2
1
18
拢896,812 in cancellations against 拢10.64m in sales.
8.4% of revenue that sat in the same column as the money that stayed, and most people never separate it out.
One SUMIF. That's all it took to find.
1
17
Teaching pays the bills. Analytics happens in the evenings after marking.
Neither one is a backup plan for the other. My next move needs both, and I'd rather build the second one slowly than pretend it's a switch I can flip.
14
One wildcard saved me checking 541,910 rows by hand.
=SUMIF(A:A,"C*",E:E)
Every cancelled invoice started with C. That was the whole trick. Before you filter anything, look at how the IDs are built. The pattern tells you what to ask.
12
There's a version of me that would have found this year easy.
Stay in one job. Teach the subject I know. Stop starting things.
I tried it for a while and it was the least alive I've felt.
1
1
33
Small Excel thing that changed how I read data:
Cancelled invoices all started with the letter C. So instead of 541,910 rows checked by eye, the formula became one line:
=SUMIF(A:A,"C*",E:E)
The asterisk does the work. It means 'anything starting with C'.



