Jun 10
Day 20/90 β
Built a Log Analyzer & Report Generator using Bash.
Features:
πΉ Input validation
πΉ Error & failure detection
πΉ Critical event tracking
πΉ Top 5 recurring error analysis
πΉ Automated report generation
πΉ Log archiving
#90DaysOfDevOps #DevOps #Linux #Bash #Automatio
9
May 18
Day 3 #90DaysOfDevOps with @TrainWitShubham Bhaiya
20 Important Linux Commands to Study
2
2
5
107
Day 10 of 90 Days of Becoming a DevOps God.
- Back in the college city. Last 20-25 days of this freaking chapter.
- Today learned and implemented IAM in AWS β Identity and Access Management. Basically who gets to do what inside your AWS account. Simple concept, but incredibly important when things go wrong in real teams.
- Also went through Configuration Management theory. Still not 100% clear on why it's needed at scale β will make more sense once I see it in action I think.
- And then something I've been avoiding for months β DSA.
Opened Linked Lists today. Almost forgot everything. Like meeting someone you used to know well and drawing a blank on their name. Embarrassing but necessary.
Getting back to the DSA grind properly from now. No more avoiding it.
Nothing groundbreaking today. Just showing up.
Day 10. π§±
#90DaysOfDevOps #DevOps #buildinpublic
3
26
Recently completed my DevOps Engineering training, but Iβve learned that real growth doesnβt end with certification it begins with consistency.
So Iβm starting a #90DaysOfDevOps journey, building and documenting my learning publicly as I grow through real systems and hands-on
3
5
37
Day 9 of 90 Days of Becoming a DevOps God.
- Skipping the day count for the last 5-6 days. Counting nothing when nothing was done.
- Went back to my village. And the moment my environment changed, everything else changed with it. No routine, no structure β just sleeping, scrolling, and somehow clocking 38 hours on Instagram in less than a week.
- Didn't even feel it happening. That's the scary part.
- There's a line in Atomic Habits that hit me hard when I thought about it β "You do not rise to the level of your goals, you fall to the level of your systems." And I had zero systems back there. Just vibes and a bad wifi connection.
Anyway. Back now. Getting back on track starting today.
- Learned a chunk of backend security concepts β
Authentication vs Authorization, MFA, Sessions & Cookies, Stateless vs Stateful, JWT & API Keys, OAuth2, OIDC, RBAC, token theft, encryption, timing attacks.
Heavy stuff for one sitting honestly. But it felt good to be back doing something real.
Done some internship work too.
Day 9. Back on the bricks. π§±
#90DaysOfDevOps #DevOps #buildinpublic
6
37
Day 3 of 90 Days of Becoming a DevOps God.
12 hours in college. Twelve.
Sessions on Low Level Design and Frontend through Java in college β honestly not very useful when you already think in React components. Spent most of it half-asleep because what else can you do at that point.
College ends at 5. Reached home at 8. Bus travel is a special kind of suffering.
But somehow β still showed up.
Finished Jira theory, and got into the good stuff: Virtual Machines, EC2, and Azure VM β how they actually work under the hood.
Done some internship work.
One thing that clicked today: A Virtual Machine isn't just "a computer inside a computer." It's isolation. Your app gets its own world β its own OS, its own resources β completely separate from everything else. EC2 and Azure VM are just cloud vendors handing you that world on demand. No hardware, no setup, just spin it up and go.
That's what DevOps is slowly starting to feel like β less theory, more "oh, so THAT'S why teams do it this way."
Exhausted. But Day 3 is done. π§±π§±π§±
#90DaysOfDevOps #DevOps #buildinpublic
1
5
75
Day 2 of 90 Days of Becoming a DevOps God.
Today was absolutely hectic.
Full Stack Java sessions from 10 to 5. Reached home at 6:15. Internship work till 12:15 AM β yes, midnight β and if I'm being honest, reels were playing in the background the whole time. Still a work in progress.
Somehow squeezed in some DevOps prerequisites and started a lecture on Jira β couldn't finish it, continuing tomorrow.
Jira is basically the whiteboard your entire team lives on. Tasks, sprints, bugs, progress β all in one place. In real teams, if it's not on Jira, it didn't happen.
Not my most focused day. But I didn't skip.
That's Day 2. π§±π§±
#90DaysOfDevOps #DevOps #buildinpublic
3
49
Day 1 of 90 Days of Becoming a DevOps God.
Not gonna lie β wasn't 100% in today. Still distracted, still shaking off 41 days of silence. But I showed up.
Covered the foundations today:
Observability, Reliability & Recovery, Automation, Environment & Config Drift, Software Delivery Lifecycle, CI vs CD vs Continuous Deployment, and the DevOps Mindset.
One that hit different β CI/CD.
Continuous Integration = merge and test code constantly. Continuous Delivery = always ready to ship. Continuous Deployment = it ships automatically. Three terms, one pipeline, zero excuses for "it works on my machine."
Showed up. That's Day 1. π§±
#90DaysOfDevOps #DevOps #buildinpublic
4
33
"Today feels like a blank page" β that was my last tweet, posted on 7th March.
bcz I procrastinated the whole day watching reels and series, and it's been 41 days since then. No posts. My 100 Days of Coding series? Stopped. Projects? Paused. The irony? I was paying for my X subscription through all of it.
I've been thinking about why I couldn't stay consistent β and honestly, it wasn't just laziness. Yes, the intention was there. But I had no clear goal. I was learning random things with no real roadmap, just doing and posting whatever, with no direction.
There's a line in Atomic Habits that stuck with me β something like: "Missing a habit once is a mistake. Missing it twice is the start of a new one." I missed way more than twice. And somewhere in those 41 days, "not posting" became the habit.
I've also realized that posting randomly wasn't giving any real value to the community β or to me.
So here's the pivot: I've started learning DevOps. The 100 Days of Coding series is on pause. A new one begins β 90 Days of Becoming a DevOps God.
Lot more to say. Will continue in the next tweet. π§΅
#DevOps #90DaysOfDevOps #Linux #BuildInPublic
3
120
Apr 12
1
2
352
Apr 11
5
309
5
472
2
158
π Day 36
Deploying a Simple Vault Environment
π github.com/MichaelCade/90Dayβ¦
#90DaysOfDevOps #DevOps
2
156
Mar 29
2 weeks PTO and we are starting in Belgium. π§πͺ
When I get home Iβm going into screenshot mode for the book! #90DaysOfDevOps imagine someone wanting to publish something from me.
My English teachers will be turning! π
7
269
Mar 14
2
174
π Day 6
Hands-On: Building a weak app
π github.com/MichaelCade/90Dayβ¦
#90DaysOfDevOps #DevOps
2
162
Just had an idea based on an issue on the #90DaysOfDevOps repo. (Almost 30k stars!, ridiculous)
What about getting 90 how to blogs from specific tooling and vendors?
We must have 90 people willing to write something useful and not using AI?
1
2
131
2
188
Learn DevOps in 90 days
βΆοΈ Watch: youtu.be/DAp1gcqiNOc
#90DaysOfDevOps
2
242