A
AbdulGoniyy Adeleke Dare
Guest
It Started with a Whisper of Doubt
Let's be honest. Starting a 100-day challenge is daunting. That little voice in your head, the one that whispers "Are you really going to stick with it this time?" was loud and clear. Every developer knows that voice. Itβs the voice of imposter syndrome, and for the first few days, it was my constant companion.
But then, something incredible happened. Day by day, commit by commit, that voice started to fade. And this morning, an email from the KodeKloud Team silenced it completely:
Hi Dare,
Big congrats - youβve successfully completed 25 tasks in the 100 Days of DevOps journey!
Youβre 25% closer to the finish line.
Youβve already done more than most ever start.
That hit me hard. "Youβve already done more than most ever start." It was external validation that the small, daily efforts were compounding into something real. The journey was no longer about proving the doubters wrong; it was about proving my own commitment right.
The Power of a Public Logbook
To keep myself honest, I decided to treat my GitHub repository as a public logbook. Every single day, I commit my solution scripts, my notes, and the original task. No hiding, no skipping days.
It's my single source of truth and my ultimate accountability partner.
You can see my entire journey, warts and all, right here:
My 100-Days-of-DevOps GitHub Repo
Hereβs a snapshot of my progress tracker. Seeing this fill up day by day has been one of the most satisfying parts of the journey.
From Theory to Tangible Skills (The First 25 Days)
This isn't just about reading documentation. The #100DaysOfDevOps challenge throws one into the fire with hands-on tasks for a simulated company, xFusionCorp.
In just 25 days, I've tackled:
- Linux Fundamentals: From user management and SSH hardening to wrangling SELinux.
- Web & Application Services: Setting up, securing, and fixing Apache, Nginx (with SSL & Load Balancing), and PHP-FPM.
- Database Management: Rescuing a broken MariaDB service and setting up PostgreSQL.
- Automation & Version Control: Writing automation scripts, setting up cron jobs, and mastering Git workflows (branching, merging).
What I've Really Learned in 25 Days
- Consistency is a Superpower: An hour of focused work every day is infinitely more powerful than a 10-hour coding binge on a weekend. It builds a momentum that becomes unstoppable.
- Document for Your Future Self: Writing notes when the solution is fresh in my mind has already saved me hours of re-Googling. Your future self will thank you.
- Embrace the Grind: The real learning happens when things break. Troubleshooting a failing service or a cryptic error message has taught me more than any perfect tutorial.
A Massive Thank You!
I couldn't have done this without the incredible KodeKloud team. Thank you for building a challenge that values hands-on skills over theoretical knowledge, all for free. And to the community, your support and encouragement mean the world.
On to the Next 75!
25 days down, 75 to go. The imposter syndrome is quiet, and the excitement for what's next is deafening. Jenkins, Ansible, Docker, Kubernetes... I'm coming for you.
What challenge are you taking on right now? How do you fight your own "inner critic"?
Let's talk in the comments. Your story might be the motivation someone else needs to start.
Ready to start your own #100DaysOfDevOps journey? Sign up here!
devops #100daysofdevops #kodekloud #linux #motivation #beginners
Continue reading...
