4 ms·
Wasn’t the idea of DevOps to put Dev and Ops engineers (two distinct roles) in one team? So instead of the Dev team working on code and testing it, and then th
by leokennis 6y ago
Wasn’t the idea of DevOps to put Dev and Ops engineers (two distinct roles) in one team?
So instead of the Dev team working on code and testing it, and then throwing it over a silo wal to the Ops team to run it in production, now they collaborated from the start to in the end ship good quality code?
When was it decided this meant one person had to know two jobs?
- pjmlp 6y agoWhen HR decided that it was the same thing as a systems engineer. Just like one needs to take care with architecture roles, because for lots of companies it is just project management with another name.
- icedchai 6y agoI applied for an architecture role once. It sounded interesting in email. Once I got to the phone screen part, they gave me a huge sales pitch, then told me I'd be working in Word and Powerpoint all day. "This is not a hands on position." Uh, no thanks. That's not architecture.
- oweiler 6y agoThat was the original idea but like almost everything in IT it got perverted until it was something else.