|
|
|
|
|
|
by levythe
2361 days ago
|
|
|
I'm glad I'm not the only one who thinks like this. Every time I read someone referring to, "a DevOps," I wonder what they think they're referring to. No one person is going to be everything you need for effective development and operations combined outside of small, extremely focused scope. DevOps is about avoiding the, "Just throw it over the wall," mentality, not making one person handle the whole thing. |
|
|
This and
>DevOps is about avoiding the, "Just throw it over the wall," mentality, not making one person handle the whole thing.
this are why it's now part of my interview process when I'm interviewing for a new role "how does your company/team define DevOps?" and I listen very closely for things that sound like 'over the wall-Ops'. Admittedly having the fortune at this point in life to be quite judicious about the answers given.
Ostensibly, if I'm applying for a 'DevOps' role, I shouldn't have to do this if the job description is written well enough, yet even then this has become a learned behavior even when coming across the rare well-articulated job req.