» First World Problems

Not being able to do anything without permission
Working as a Software Engineer for a University, we use to be able to release non-tested buggy software to our clients without so much as a question raised.

Now, we have to fill in a 7 page document that proves it has been tested and who is to blame when it goes wrong. Then attend a meeting to discuss and approve or deny the document, which is ridiculous in its own regard because no-one at this meeting has a clue what these systems are. To then release the same non-tested buggy software because the fucking client tests it by just looking at the pages and clicking some buttons.

We can't even make the release ourselves, we have to get someone to basically open a explorer window the live server and get the contents of the release folder copied over. If we make any DB changes then we have to get two people that sit in the same room to coordinate the release as one person can't do the same job (apparently).

All because of things like "Security" and "Responsibility" as well as documenting every change so we know what happens where. In my day it was you release, then fix, then re-release, then fix...

Kinda bleeds into the previous question a bit but it still gets my goat that I have to jump through so many hoops to make a release but someone higher up than me can take down the entire network and write a "retrospective" document which basically says "whoops"
(Thu 1st Mar 2012, 16:25, More)