"When the user does blah blah blah should we spawn a new thread for blah blah or block the current one until blah blah blah fucking blah?"
I DON'T KNOW! I DON'T CARE! I'M GONNA STAB A DRY ERASE MARKER IN MY EYE JUST SO I CAN GET OUT OF HERE!
One thing that I noticed was running rampant today was people copying each other's "bullshit jargon" speech patterns. For instance, one guy in the first meeting kept referring to different product cycles as "iterations" and kept using iterate as a verb substituting the verb "work". Like, "we'll decide on that as we iterate through." I've never heard anyone at this company use the word iterate in that way before and it was clear that the guy was doing it to try to sound cool (yeah... we're all geeks at this company...) but before long, three other people in the meeting were doing it. DEATH TO YOU ALL!
In the second meeting, one guy pronounced the word "status" the way the British do. State-us, with a long "a". Not very common but god damn if everyone else didn't pick it up and start doing it immediately... even the guy with the southern accent. And then, when I said the word the way I always do, they all kinda choked on it for a second, and in their responses to me, they made sure to incorporate it with this newly accepted pronunciation, as if to scold me for not getting with the times. Fuck you guys. I'm sticking with the tried and true, patriotic American pronunciation. Wankers.
I think I'm gonna come up with some really stupid term for something and try to get everyone to start using it. For instance, whenever I refer to doing a build, I'm gonna call it "twisting the bits". So today, the conversation might be:
"Hey Steve, have you done that build yet?"
"I'm twisting the bits right now, give it about five more minutes."
but tomorrow, it'll be:
"Hey Steve, have you twisted the bits yet?"
"Twisting as we speak, compadre. And may I take this opportunity to compliment your fine word choice?"
Baaaaaaaaaa!, say the sheep.
God damn I'm hungry.