... and so it begins. The line in the sand was just drawn. The decision from the higher ups to ratchet down the 'separation of duties' was kicked off this afternoon in a surprise fashion.

You know.. in case folks would have advanced warning and hide their malfeasance versus having a better process worked out for our releases to minimally impact our users.

As always I was leading the charge and I was the first to require two releases *AND* one of my app users is just now demanding an emergency release (NOW!).

Objectively it will be interesting to see if a tide of managers, users, directors, etc can rise up fast enough to quash this, or even if the high-higher ups will budge on their view.

As a person living this I know (I've been here before in other companies) this will be a grueling new process that will just make folks bitter, put a cramp in the entire company's reaction time, hurt team image, and we'll get all sorts of undeserved flack.

Next stop - SlowRelease-ville and disappointment.


After today I get to go home and fashion and email explaining how these changes to my side work is going to run somewhere along the 1k-1.25k range and the work handler won't like that response.. but what can I do when it's another 18ish hours of work that was not outlined in the original spec? The alternative is to fix the bugs, send the project, and get my cash.. hopefully it won't spook this guy into canceling the whole project. Fuck this project.