Procedural Approval

4 thoughts on “Procedural Approval

  1. …yea okay i quit, good luck with your S888ty trainwrek of a website

  2. Wow…that is so freakin’ familiar!

    Client gives developer/programmer the passwords to fix their problems with their software and then doesn’t give the help the authority to use them. In one word: Sheesh!

    I agree…if you didn’t want to give the permission to use the passwords in order to fix the problem, then DON’T GIVE THEM OUT!!!!!!

    If a client gets pissy about this, dump ’em and let them go hang

  3. If you don’t want someone looking at the database, don’t give them the password to do so. The hoops to jump though of approval to get said passwords i can sorta understand, but only sorta.

  4. I feel like that dude must have a day job in the public sector. Possibly on a municipal level.

    “We want you to do this job.” ‘Okay, so I’ll start by….’ “Oh no no no… First, write all that down and email it to four different people who will each respond with ‘Reply all’, but never actually read the other messages in the train. Then when twelve more people have weighed in, we’ll start to think about forming a committee to begin the process of considering your proposal.”

Leave a Reply to SirReal55 Cancel reply

Your email address will not be published. Required fields are marked *

*

*

*