A month ago, I decided to start learning Tailwind CSS. I already had some background in regular CSS, so I wasn't starting completely from zero — but Tailwind is a different way of thinking about styling, and I wanted to learn it properly instead of just copying classes from tutorials without understanding them.
I chose to learn it on Scrimba, and one month in, I'm not finished with the course yet — but I've learned enough to already notice how differently I think about building UI now. Here's an honest look at where I'm at.
Why Tailwind, and Why Scrimba?
Learning Tailwind was actually part of a job requirement for me, so I needed to get comfortable with it quickly. A colleague of mine recommended Scrimba as the place to learn it, and after checking it out, I understood why.
Where it all started from
What I've Covered So Far
In my first month, I've worked through:
Element sizing — how Tailwind handles widths, heights, and spacing with utility classes.
Colors — Tailwind's color system and how much easier it made styling feel compared to writing custom CSS values.
Padding and margin — the spacing utilities, which turned out to be more challenging than I expected (more on that below).
Headers and footers — building out real page structure, not just isolated components.
To be honest, nothing clicked right away. It wasn't until I went through the material a second time, with the docs open alongside it, that things finally started making sense.
The syntax I was learning
The Moment I Almost Gave Up
Here's the honest part of this story.
When I got to the lesson on padding and margin, I hit a wall. The assignment that came with it was harder than anything before it, and at one point, I genuinely felt like giving up. Understanding the class names was the hard part — I kept mixing them up, unsure which one meant padding and which meant margin, or which side of the element I was actually targeting.
What got me through it was a combination of Scrimba's guidance built into the course and the official Tailwind docs, which I ended up leaning on heavily. Slowly, piece by piece, things started making sense.
The moment I finally got the assignment working, I felt genuinely proud of myself — not just relieved, but proud.
More than anything, that moment taught me patience. Even with all the guidance available, I still didn't understand it right away — and I had to accept that and keep going anyway instead of expecting it to click instantly.
What Scrimba Gets Right:
The combination of video + interactive code + guidance kept me engaged in a way passive video-only courses hadn't
Having the docs recommended alongside the course meant I wasn't just following along blindly — I was learning to actually read documentation, which is a skill on its own.
Would I Recommend It?
Yes — and not just to beginners. I'd recommend learning on Scrimba to anyone, whether you're a beginner, intermediate, or advanced developer. It's the interactive, hands-on experience that makes it work — you're not just watching someone else code, you're actually writing and testing it yourself as you go.
If you want to check it out yourself, here's the link I used to get started: https://scrimba.com/?via=community
What's Next?
I'm continuing the course from here, and my next milestone is learning font classes, before moving on to building a plant enthusiast blog as a project to put everything together. I'll probably write a follow-up once I'm done with the full path — this felt too early to call it a full review, but one month in already taught me more than I expected.
If you're learning to code too, I'd love to hear what's worked for you. Feel free to connect with me on X @annie_fumoh or Instagram @theaniekansway.
Top comments (0)