Linux 🐧 | Cloud ☁️ | DevOps 💻 | Security 🪖 Exploring and sharing tech insights through my writings ✍️ Come along on this journey! 👋
Bharat
Joined September 2020
- Tweets8.7K
- Following627
- Followers17.1K
- Likes3.4K
🧵 What Big B’s ABCL failure teaches us about a DevOps career
ABCL tried to do everything at once - movies, TV, music, events, distribution & celebrity management.
Big ambition.
Weak foundations.
And that’s surprisingly relevant to a DevOps career. 👇
🤖 Made with AI
SSL certs don’t expire… they just wait patiently for the worst possible moment to remind you they exist. 😂🔐
Renew them before they expire 👍
Rakesh Jain retweeted
Shell Scripting Interview Guide!
A Thread with 20+ mid-level to advanced Linux shell scripting interview questions with examples and answers 👇🐧
Rakesh Jain retweeted
Mastering DockerFile!🐳
A guide of 20+ examples for all the #developers , #DevOps Engineers and #Linux Admins👇
Absolute operational failure by @Lufthansa. Keeping passengers trapped on a plane for over 3 hours after a massive delay and diversion, then leaving them stranded without transport at 3 PM? Pathetic customer care. Do better. 🛑 @Lufthansa_India
@lufthansa @Lufthansa_India What’s happening with LH755 BLR–BEG via FRA?
Reached BLR at 12 AM. Flight delayed 3.5 hrs, diverted to Mumbai, landed ~9 AM. Passengers kept onboard till 12:15 PM, then stranded with no clear updates. Hotels offered, but no transport even at 3 PM.
Rakesh Jain retweeted
🧵 What Big B’s ABCL failure teaches us about a DevOps career
ABCL tried to do everything at once - movies, TV, music, events, distribution & celebrity management.
Big ambition.
Weak foundations.
And that’s surprisingly relevant to a DevOps career. 👇
🤖 Made with AI
10/
Your DevOps career is a production system.
Build strong foundations.
Reduce complexity.
Automate wisely.
Remove SPOFs.
Measure impact.
Scale when ready.
Don’t build an ABCL-sized career on startup-grade foundations. 😉
#DevOps #SRE #PlatformEngineering #CareerGrowth
9/ The real lesson
Don’t ask:
“How many technologies can I learn?”
Ask:
“How much complexity can I reliably manage?”
That’s the journey from Engineer → Senior → Staff → Principal.
ABCL nearly destroyed Big B financially.
But he rebuilt.
Production failures, bad migrations and wrong architecture decisions don’t end a DevOps career.
Not learning from them might.
7/ Titles follow capability
Don’t optimize for:
Senior → Staff → Principal.
Optimize for:
Bigger problems → Better solutions → Greater impact.
The title follows.
6/ Build an adjacent career
Don’t randomly collect technologies.
Build a path where each skill strengthens the next:
Linux → Cloud → IaC → Kubernetes → Platform Engineering.
Your career needs architecture too.
5/ Avoid the “hero engineer” trap
If only you know production, Kubernetes, AWS, Terraform and DR…
You’re not a single point of expertise.
You’re a single point of failure.
Document. Automate. Share.
4/ Manage complexity
Your production system has technical debt, toil, incidents and cloud costs.
So does your career.
Don’t just add skills.
Learn to reduce complexity and improve reliability.
3/ Automate the right things
ABCL scaled complexity before stabilizing the business.
Same in DevOps.
Don’t automate chaos.
Simplify → Standardize → Automate → Scale.
2/ Don’t confuse “more tools” with “more capability”
ABCL had many businesses, but complexity doesn’t automatically create value.
The same happens in DevOps.
Having 40 tools on your resume doesn’t make you senior.
Knowing why, when and where to use 5–10 tools effectively does
1/ Build foundations first
ABCL expanded aggressively before proving that its core business model was sustainable
Don’t rush to Kubernetes/AI/Service Mesh & 20 tools
Master the basics:
Linux > Networking > Git > Cloud > CI/CD > IaC > Observability
Strong foundations compound
