Things I want from Devs as SRE/DevOps
&gt; If you’re a Software Engineer&#x2F;Developer, then consider that a service (at least, for me), is a piece of code running in a live production system, that YOU wrote, only YOU know how it works, thus YOU own.<p>I&#x27;ve grown unfond of this attitude. I most certainly don&#x27;t own it.  I have no IP rights to it at all.  We&#x27;re both being paid to solve different facets of the same problem.  Coming at me  with &quot;this is your problem&quot; isn&#x27;t going to foster a collaborative environment with me.  Which is much more pleasant than an adversarial environment.<p>Also:  I&#x27;m not the only one that knows how it works, it&#x27;s been peer reviewed in no small part to reduce my bus factor. All documentation requested is perfectly reasonable, and should be part of the organizations standard operating procedure.<p>If it&#x27;s not part of the SOP, then no, you wont have those things.  You need to work at a cultural level to change that, and for that you&#x27;re much better off making allies than anything else.  Make it clear how those things help you, and what you&#x27;ll do to make the developers life easier when you don&#x27;t need to worry about the basics.  If altruism fails you, you can usually count on people to act in their own best interests.