sbiewald346618dSome of the problems you describe are "we have to few people" - devops does not mean "fire the admins" or broader "fire the experts". And certainly never "fire the business people"!
The quality drop means bad management and QA - which can be fucked up independently of devops.
By the way I do doubt serverless is the way to go in the most cases... It's just one way to do and not correct in all cases - the same with monoliths.
And to your quote about the mechanical engineer: One knows (or should know) the world - and with it your work - will change.
@sbiewald "we have to few people" - this, in my experience, is reality in most organizations though.
"quality drop" I was referring to was Code quality, not bugs. This is two fold. First for new developers it's too hard to properly pick up fundamentals as concentrations is more and more on Operations now. Secondly it's reshaping of culture values - now it's a mix of programmers/operations/aws-gurus/juniors/... - code quality is not valued the same by everyone as before, need to push old truths all over again.
Finally regarding the change, I'm embracing it - I'm just re-assesing options I and others like me have, the ones who end up in this industry mostly because of love for writing code and still want to do that for upcoming time. It's not a fight against industry, it's looking for job satisfaction.