Fanboys can't be seniorsCan you be critical of your favorite tool? Can you see the merit in using alternatives?
Time for a hot take:
Fanboys can’t be seniors
What do I mean?
First, what I don’t mean:
I don’t mean you can’t have a favorite tool, language, framework, IDE, tech stack, RDBMS, or whatever. Favorites are fine. In fact, most highly-qualified professionals have favorites, for very legitimate reasons.
What I do mean:
Given that you (probably) have a favorite tool in every one of the above mentioned categories, can you be critical of it? Can you see the merit in using alternatives? Can you respect those who don’t agree with your choice of favorite? What is your least favorite thing about your favorite thing?
I really like the Go language. For the last several years it has been my go-to language for most programming tasks. But there are things I dislike about it. I often wish some functional programming paradigms were available to me. I dislike many features of the standard library (the default JSON (de)coder must read the entire stream into memory before parsing… WTF?) I could go on-and-on.
So I like Go, yes. But I’m not a Go fanboy, at least as I understand the term.
I don’t like Go to the point of being blind to flaws, or unable to criticize it. I don’t like Go to the exclusion of other languages. I certainly don’t try to belittle people who are more comfortable with some other language.
Reader question: What kind of role should I look for when starting a career in DevOps?
“Is it a good idea to look for specifically DevOps roles, or other positions like sys admin, engineer, etc?”
How long should your résumé be?
What I think is more important than a résumé's length is that the first half of the first page tells me: What role are you looking for, and what level of experience do you have?
Improve your software delivery