On 17.09.2019 and in less than 36 hours of the exam, I got an email that I passed from the first try and I'm now a Certified Kubernetes Administrator (CKA) 🎉🎉
It's not my first performance-based exam, I had before
On 17.09.2019 and in less than 36 hours of the exam, I got an email that I passed from the first try and I'm now a Certified Kubernetes Administrator (CKA) 🎉🎉
It's not my first performance-based exam, I had before
Ahmed AbouZaid
08/08/2019
Agile, Management, Work culture
Comments
What I like about working in startups and small-mid companies is that they’re flexible and you can have a visible change and a direct impact. Ironically that's the same reason why heroes and heroism find their way in that ecosystem.
If you have been working in the IT industry for some time and especially in startups, mostly you would have met that kind of people at work ... heroes!
So who exactly is a "hero"? (sometimes also called "Ninja")
Heroes are some people at work who can do crazy stuff. They are doing everything needed to get things done. They have all kinds of access and privileges. They know all the info that cannot be found anywhere. They are doing the hard tasks that only they can do and solve problems that no one else can solve. However, all of that’s mostly done with no clear mid- and long-term planning, undocumented, and on an ad-hoc style! (so being a hero is not about performance but work practices!)
Managers mostly like them because they, the heroes, get lots of things done quickly for the company. In fact, heroes are not necessarily bad people, assholes, or jerks. Sometimes they are also good and nice but their way of work is just harmful!
Wait a minute! Doesn't that sound good? Many things are getting done fast and on time! Isn't it better if we have more of those heroes?
NO! Unfortunately not! All of that comes at a cost!
First of all, heroes are heroes because the rest are "normal". Those heroes simply limit the other people in the team and keep them from growing, and the only way to pair with heroes is to be another hero, just like them. But in the end, a company is like a film, there is no film full of stars!
Not only that but also wrong expectations raised against other team members when they don’t do the hero-way! Why aren’t they the next hero?
What heroes are actually doing is like getting a loan, you have a lot of money to spend now, but you drown in debt later ... the technical debt. Maybe everything works "just fine" for now, but later, many things will not.
Teams (and maybe the whole company) will end with fire fighting and an ad-hoc work style. And then when you realize what was wrong, the cost of re-engineering the mess, and fix it, is usually horrible.
When heroes are off or on a vacation, other people tend to be afraid of making changes, because it's not clear how things are working. Furthermore, when heroes are not there, many incidents happen because most of the time they keep things “just work”.
Also if the heroes are not communicating their work (through documentation, short presentations, awareness sessions, etc), then their absence due to any reason (death, accident, etc) means that their team and maybe the whole company are paralyzed.
After all, those heroes are humans and have their limits, hence companies cannot depend on people "individually" but as a "team".
It's not so hard to find traces of hero practices … you just need a closer look, especially on the team level.
At the end of the day, when you realize how heroism is harmful to the company, it's probably too late. Mostly you will be on the horns of a dilemma!
If you keep heroes and their way of work, the longer they stay the harder to change. And if you tried to get rid of those practices quickly, you put yourself and the company in an ultimate risk!
It's also worth mentioning, and believe it or not, having heroes as a part of a company is not really a problem per se! In the early stages of the company life, they could help the company growth a lot. The actual problem is when the "hero-way" becomes the default way to work with no proper plan to move towards sustainability.
Unfortunately, there is no silver bullet to fix this. But here are some takeaways you could think about:
That's all! And I hope you have more sustainability and less heroism :-)
Few years ago when I started to do more CI/CD practices, I wrote these 2 posts:
Nowadays, CI/CD become a market de facto standard. So what's next? "Cloud Native"!
Ahmed AbouZaid
21/05/2019
Agile, DevOps, Planning
Comments
I've been working professionally in the tech industry for more than 7 years. The change has been always one of my things. I started to do that starting from my first day in this career!
And that's actually why I love the "DevOps movement", because it's about "change"!
Automation and infrastructure as code became a really important thing in tech industry. Actually the became a de facto!
But in real world and especially in startups world when you have limited
Ahmed AbouZaid
04/04/2019
Golang, Monitoring, Prometheus
Comments
Recently I played with Prometheus more deeply. I wanted to expose some metrics from a REST service written in Golang. I needed to deal with Prometheus instrumentation
As I always say, I like to avoid manual boring work, and manual repetitive work is always boring for me! So I used to automate my system I use on my laptop with most of stuff I used to use.
Although I'm not big fan of changing my main system too much. And as I'm the author of
One of pretty interesting components I worked with it last 2 years was "Keycloak" by Red Hat! Keycloak has many use cases, and I did see many projects use it in different ways especially
Ahmed AbouZaid
06/01/2019
DevOps, Golang, Metacognition, Terraform
Comments
Beginning of 2018 was my real expose to Golang. It's almost a year now! (before that was just playing around where I can just
Hello, my name is Ahmed AbouZaid, I'm a passionate Tech Lead DevOps Engineer. 👋
I specialize in Cloud-Native and Kubernetes. I'm also a Free/Open source geek and book author. My favorite topics are DevOps transformation, DevSecOps, automation, data, and metrics.
About 10 years ago, I used SaltStack extensively and wrote my top 10 best practices for SaltStack formulas . Today, I do the ...