not one that had the authority to drive changes outside of writing content.

HA HA HA HA wait, are they serious? Jobs I've worked, especially software, we were lucky if we got the fucking UI changes with enough time to update the documentation before release.

Thank you, everyone. Rest assured that I am far more upset about this than ltc is. This is a boy she can’t stand already and his opinion of her means nothing at all. I got a bland response from her usually wonderful teacher that she would pass it along to the people who usually monitor lunch. However since the principal and vice principal are among those people I’m giving it until Monday for someone to get back to me before I contact them directly.

HA HA HA HA wait, are they serious? Jobs I've worked, especially software, we were lucky if we got the fucking UI changes with enough time to update the documentation before release.

When I explained to my management chain - again - that my feature writers update the release notes a minimum of 5 times a week because PMs didn't think to mention a change was going out, they made horrified noises. Again. Just like every time.

I like my job and my team, but there are times that I want to play IRL whack-a-mole.

When I explained to my management chain - again - that my feature writers update the release notes a minimum of 5 times a week because PMs didn't think to mention a change was going out, they made horrified noises. Again. Just like every time

Hold up, are you actually me posting from my old job??

Hold up, are you actually me posting from my old job??

AHAHAHAHAHAHA oh it's not just my pack of PMs who don't do this?

I've met most of them in person, and they're good people. They just have this blank spot in their brain around "accurate documentation is part of feature release, yes really, our C-team leader emphatically said that".

I know we said "code freeze", but what we actually meant was "code freeze except for these three things which are too important to leave out. And those three things can change at any minute. And we will tell you nothing."

I was able to gently guide (er…bully ) the teams my team supported into more rigorous release practices eventually but it was a struggle.

I know we said "code freeze", but what we actually meant was "code freeze except for these three things which are too important to leave out. And those three things can change at any minute. And we will tell you nothing."

AHAHAHAHA.

The number of times I had to mention in Jiras last year that we were in a release freeze, no really...

We’re going to hear next Tuesday how my employer plans to respond to all the everything. We’ve already had hiring and traveling freezes. I think the next step is stopping contributions to our retirement funds and then layoffs. No idea where my department will land. I wish I still had a Xanax prescription.

Documentation folks, as a former software QA manager I hear you, and it's giving me unpleasant flashbacks.

"What do you mean, we actually have to run the entire test suite on this last-minute emergency fix before it goes into the release? That'll take hours!"

"Great. You can spend those hours documenting what the new fix does."

"But that's the docs team's job!"

"Have the docs team even seen the new code?"

"Well, no ...."

face from The Office