My name is Simon and I am
a DevOps Engineer.
I have always been really passionate for Computer Science and living a life of a DevOps
allows me to take advantage
of the whole stack of technologies ranging from networking and telecomunication, through
large scale distributed computational systems,
up to software development. I tend to have decent orientation in a variety of solutions
across previousely mentioned domains rather than specialize
in a narrow field or application. I value this approach because it allows me to be
well-rounded which is crucial in making archetectural decisions.
My goal is to become a DevOps Tech Lead - a good one. (UPDATE: Already a Tech Lead, still
working on the good one part.)
Below you can find some concepts that
I follow and I am deeply passionate about:
I tend to think of myself as a good leader that seeks a place to develop into comprehensive
one.
Eager to take advantage of opportunities and learn how to improve in this domain. Always
trying to be a good team player and being considerate and adaptive to other team members.
Love collaboration where I get to see what others perspective and widen my horizons.
Here are some of the principles that I think are crucial in being a good DevOps:
1. Everything is code
2. Develop and maintain
3. Least privilage always
4. Everything is observable
5. Automate and automate and automate...
6. Self serviced product
8. Design smart and improve
Making architectural decisions is the same as it used to be at the beggining when you worked
on the project by yourself - like a driving a car for the first time exciting to go wherever
you want.
Doing that in professional life is the same except for children in the
backseat(team members), mother in law in the front seat(manager) and the car behind you
honking(buisness unit).