Operations is not Developer IT
I am sorry but as an application developer, I think this is all wrong. I&#x27;ll thank my infra team today for not being assholes like this guy.<p>1. Application developers are your users. If we application developers took offense every time a user tells us that things are not working, we&#x27;d be pretty pissed off all the time. Educating and empathizing with your users is part of your job.<p>2. Talking about how it was better before: QA teams sure do buffer a lot of crap. They also cost a bunch and slow down time to release. Yes agile is causing problems. The bureaucracy and stiffness of organizations before agile was no nirvana either.<p>3. By your own affirmation you treat applications as black boxes that should be deployed using a runbook that should just work. This is ridiculous. Application&#x27;s ownership is shared between everyone who works on it.<p>4. And yes, as developers, networking or physical drive space are things that we tend to abstract away. Maybe if the infrastructure people were involved in development discussion earlier, they&#x27;d be able to raise their hands and say: wait a minute, you&#x27;re going to blow up our logs.<p>This all feels like someone who used to not do anything suddenly being asked to take part in what&#x27;s happening...<p>EDIT: apologies for the strong language and sounding like an asshole myself, but I certainly feel irritated when someone takes the time to write a 5000-word article complaining about whiny developers who thought they could own ops but actually don&#x27;t know anything and scream for help when they themselves are the cause of all evil.