Conceptually, I think "DevOps" always smells like an attempt by companies who have long since lost any employees who care about the business, to refill the lost-unicorn role of some early hires (or founders) who understood the total urgency of the business logic at the same time as being able to deliver working code. You can't exactly pay your way out of that or expect to write a manual to define the role! What would work better would be what the lost unicorn had, presumably:
• Constant joint meetings between design, code and marketing
• Frequent conversations with top management on the business side
• A share of equity in the business
Then you don't have to call it "DevOps", you call it a co-owner who knows how to code. But of course, the MBA's never like the guy who does the code, so they invented this ludicrous fake role after they kicked that guy out.
3 comments
[ 4.7 ms ] story [ 18.0 ms ] threadConceptually, I think "DevOps" always smells like an attempt by companies who have long since lost any employees who care about the business, to refill the lost-unicorn role of some early hires (or founders) who understood the total urgency of the business logic at the same time as being able to deliver working code. You can't exactly pay your way out of that or expect to write a manual to define the role! What would work better would be what the lost unicorn had, presumably:
• Constant joint meetings between design, code and marketing
• Frequent conversations with top management on the business side
• A share of equity in the business
Then you don't have to call it "DevOps", you call it a co-owner who knows how to code. But of course, the MBA's never like the guy who does the code, so they invented this ludicrous fake role after they kicked that guy out.