3 ms·

Oh nice, this should be turned into like a bingo card, let's see: > I could not order a corporate laptop until I joined the project. Corporate laptops were bac

Oh nice, this should be turned into like a bingo card, let's see: > I could not order a corporate laptop until I joined the project. Corporate laptops were backed up with a minimum of 2 months to deliver one. Huh, that's some softball right there! The worst I've seen is 7 months! > To get the code into the repository it had to be sent via the project manager on a USB stick by copying the entirety of your source code onto it okay that's scary > Did I mention that any copying of files off of a corporate laptop was forbidden? Doesn't that contradict the USB process? Otherwise that's 'standard' > In the sprint planning meeting the scrum master would demand that we “commit to the sprint.” The bodyshop minions would all meekly agree Seems minions know their protests will be ignored, just like the author's were, so why even bother. I have seen 'minion-esque' behaviour a lot, but not the degree of brain-dead behaviour from management described there. > Also these days I avoid any project where I won’t be in a position to help steer things before they can go that superluminally off-track. Neat!

dcminter 4y ago
> Huh, that's some softball right there! The worst I've seen is 7 months! That's the special kind of impressive. > Doesn't that contradict the USB process? Otherwise that's 'standard' Yeah, I thought I might not have made that clear. They were allowed to copy files onto the laptops, just not off them. So with the wild cut&paste integration situation it meant that none of the actual developers could be aligned with the code that was actually being compiled because we could never update to the master copy. The moment I realised that the terrible PM was doing diff by eye instead of, you know, using the diff tool, was when I should have walked away. I stuck it out way too long in retrospect.
- cmeacham98 4y ago
  How did you ever get the codebase in the first place to work on? Or was your part writing something completely from scratch?
  - dcminter 4y ago
    Integrating a (third party) white label product into the enterprise's existing system. So from scratch effectively. And yes, not having any access to the system with which we were supposed to be integrating it was also a problem...
madaxe_again 4y ago
Most of this stinks of ISO27001 “by the book”, using some horribly rigid off the shelf ISMS to gain certification rather than creating something compliant that actually works for the org. Been there, done that, red swingline stapler.

dcminter 4y ago

> Huh, that's some softball right there! The worst I've seen is 7 months! That's the special kind of impressive. > Doesn't that contradict the USB process? Otherwise that's 'standard' Yeah, I thought I might not have made that clear. They were allowed to copy files onto the laptops, just not off them. So with the wild cut&paste integration situation it meant that none of the actual developers could be aligned with the code that was actually being compiled because we could never update to the master copy. The moment I realised that the terrible PM was doing diff by eye instead of, you know, using the diff tool, was when I should have walked away. I stuck it out way too long in retrospect.

cmeacham98 4y ago
How did you ever get the codebase in the first place to work on? Or was your part writing something completely from scratch?
- dcminter 4y ago
  Integrating a (third party) white label product into the enterprise's existing system. So from scratch effectively. And yes, not having any access to the system with which we were supposed to be integrating it was also a problem...

madaxe_again 4y ago

Most of this stinks of ISO27001 “by the book”, using some horribly rigid off the shelf ISMS to gain certification rather than creating something compliant that actually works for the org. Been there, done that, red swingline stapler.