Make the CV a bit more neutral

This commit is contained in:
Nikolai Rodionov 2024-03-12 13:21:03 +01:00
parent 4cb433f938
commit 1fe981edae
Signed by: allanger
GPG Key ID: 0AA46A90E25592AD
1 changed files with 8 additions and 8 deletions

View File

@ -20,16 +20,16 @@ css: |-
### About me
I'm a DevOps engineer with 5++ years of hands-on experience with a decent amount of tools. One of the most important tools that I love and want to continue working with, is Kubernetes. At least, until I see a better alternative. I think that containers themselves are one of the greatest inventions in development, and I'm trying to use them as long as it's possible. Also, I believe that every routine must be automated, because that's the boring job that lets people lose focus and make mistakes.
I'm a DevOps engineer with 5++ years of hands-on experience with a decent amount of tools. My main focus is Kubernetes and CI/CD.
I think that there are several things that a DevOps engineer must be able to do:
- To build reliable and stable infrastructure
- Keep this infrastructure up-to-date
- Keep all the source and instructions of this infrastructure clean and simple
- Avoid a human factor as long as possible
- And when it's not possible to avoid it, not to be afraid to take responsibility
I've got some beliefs that should be capable of describing myself
I think it's important, that before implementing anything, an engineer has understood all the requirements and checked tools that can fulfil them. I often see, how people try to use a tool for its name but not for its functionality, and hence they have to do a lot of additional work and deal with compromises. And if nothing really can fulfil those requirements, you need not be afraid of writing something new *and open-source it*.
- One should tend not to repeat oneself
- One should never edit what's constantly generated
- One should aim for lesser amount of work with a bigger outcome
- Unles something is in CI, it doesn't exist
- Human factor must be avoided when possible
- Any routine must be automated, because it's error-prone
### Experience