3 ms·

There is nothing more frustrating than being responsible for software you didn't write or had no part in writing. I don't get why management finds this so hard

There is nothing more frustrating than being responsible for software you didn't write or had no part in writing. I don't get why management finds this so hard to get. I know there is some spreadsheet somewhere with my name next to this application, but I have never touched it and until now didn't know it existed. Please don't expect me to figure it out in an emergency situation.

evgen 10y ago
Try being the ops person expected to be able to troubleshoot this dumpster fire in the middle of the night; they didn't write a single line of the breaking code either. Why exactly are they expected to know what broke and how to fix it while you can't seem to be bothered learning how the rest of your stack works?
- kelnos 10y ago
  "Bothered" is a bit of a strong word there. When the company I worked at had 30 engineers, fewer services, and fewer lines of code, I did know how almost everything worked. Now we have over 3x as many engineers, and enough services such that it would be a full time job and then some just to keep track of how everything works. Fortunately we do team/product-based on-call, so people are (for the most part) only responsible for services they work on or at least are familiar with.