mishaq posted:

that dude owns

Stymie posted:

it's kind of weird to read all these stories that boil down to "the work i do is so unimportant that i can be incommunicado for days on end and it makes no difference to anyone"

mishaq posted:

that dude owns

Buff Skeleton posted:

my company is just the tip of the corporate stupidity iceberg

Captain Foo posted:

I have occasionally answered my phone but lol at voicemail

Captain Foo posted:

it's u lol

Stymie posted:

i suppose the tradeoff of not being forced into mind-numbing teleconferences or being terrified of the phone is i occasionally have to suffer the indignity of talking to my coworkers in person and being productive

woe is me

abraham linkedin posted:

lol if you ever speak to anyone inside your office unless they have the power to fire you

Iridium posted:

celebratory update: our telecomms people have agreed to set up my VM box to play a message (which i will record to tell people to gently caress off) and then not let them leave a message.

i feel more productive already.

Bloody posted:

in a conference call just now starting

already had some random person call in

ah good our line is double booked lmao

Cat Face Joe posted:

pm books hour meetings back to back for individual projects. i call in for mine and hear a dozen people just screaming at each other. hang up cause it sure sounds like mine is canceled. turns out the previous one was as well and the current call is entering its third hour

Cat Face Joe posted:

pm books hour meetings back to back for individual projects. i call in for mine and hear a dozen people just screaming at each other. hang up cause it sure sounds like mine is canceled. turns out the previous one was as well and the current call is entering its third hour

Cat Face Joe posted:

pm books hour meetings back to back for individual projects. i call in for mine and hear a dozen people just screaming at each other. hang up cause it sure sounds like mine is canceled. turns out the previous one was as well and the current call is entering its third hour

ChickenOfTomorrow posted:

wow

why do you still work there

Mad Wack posted:

i have lived this

there is one particularly toxic group where any call with them i just go ahead and block out three hours after it

Bloody posted:

in a conference call just now starting

already had some random person call in

ah good our line is double booked lmao

Iridium posted:

oh poo poo that reminds me

in addition to my company's general conference line like the webex / skype poo poo, our phone system has several dedicated conference lines. no special access code is needed, it's for emergencies: if there's a massive outage, you can dial into just a basic phone number from anywhere at all and be on the bridge. they're not commonly used now (short of super severe network emergencies), but when i first joined the company and worked in operations it was the standard. each time we had a critical outage, they'd send out the alert and one of us would have to hop on.

but this got to being a problem because absolutely everyone could call in, and the number would spread very quickly. the people trying to work on the issue would be trying to coordinate and do poo poo, but the 'problem manager' would want constant updates, and demand that everyone stop talking to update whatever other random middle manager hopped on and demanded info. as you'd expect, this became a complete clusterfuck, so they tried to implement a rule saying that people working the issue would be on line X, while anyone needing noncritical updates would have to call line Y, where the problem manager would pop over and provide updates. except guess what: the numbers never changed. so everyone would just call in to line X anyway and start making demands. on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

around the time i switched out of operations it had become standard for people working the issue to call in to line X on their desk line, then just call one another on personal cell phones to actually coordinate work. we'd get yelled at for doing so because 'everything is supposed to be open so nobody who might have a solution is left out'. didn't stop anyone.

Iridium posted:

oh poo poo that reminds me

in addition to my company's general conference line like the webex / skype poo poo, our phone system has several dedicated conference lines. no special access code is needed, it's for emergencies: if there's a massive outage, you can dial into just a basic phone number from anywhere at all and be on the bridge. they're not commonly used now (short of super severe network emergencies), but when i first joined the company and worked in operations it was the standard. each time we had a critical outage, they'd send out the alert and one of us would have to hop on.

but this got to being a problem because absolutely everyone could call in, and the number would spread very quickly. the people trying to work on the issue would be trying to coordinate and do poo poo, but the 'problem manager' would want constant updates, and demand that everyone stop talking to update whatever other random middle manager hopped on and demanded info. as you'd expect, this became a complete clusterfuck, so they tried to implement a rule saying that people working the issue would be on line X, while anyone needing noncritical updates would have to call line Y, where the problem manager would pop over and provide updates. except guess what: the numbers never changed. so everyone would just call in to line X anyway and start making demands. on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

around the time i switched out of operations it had become standard for people working the issue to call in to line X on their desk line, then just call one another on personal cell phones to actually coordinate work. we'd get yelled at for doing so because 'everything is supposed to be open so nobody who might have a solution is left out'. didn't stop anyone.

Iridium posted:

on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

mishaq posted:

lmao what kind of clown operation do you work at

Iridium posted:

a corporation on target to hit $20bil this year, with subsidiaries that most of you have heard of and many of you use on a daily basis. but we're the parent company, so since we don't have actual revenue targets to drive a goddamn thing, we're an incestuous cesspool of stupidity (but with loving great benefits and pay, because the divisions keep meeting our financial targets lol)

Iridium posted:

oh poo poo that reminds me

in addition to my company's general conference line like the webex / skype poo poo, our phone system has several dedicated conference lines. no special access code is needed, it's for emergencies: if there's a massive outage, you can dial into just a basic phone number from anywhere at all and be on the bridge. they're not commonly used now (short of super severe network emergencies), but when i first joined the company and worked in operations it was the standard. each time we had a critical outage, they'd send out the alert and one of us would have to hop on.

but this got to being a problem because absolutely everyone could call in, and the number would spread very quickly. the people trying to work on the issue would be trying to coordinate and do poo poo, but the 'problem manager' would want constant updates, and demand that everyone stop talking to update whatever other random middle manager hopped on and demanded info. as you'd expect, this became a complete clusterfuck, so they tried to implement a rule saying that people working the issue would be on line X, while anyone needing noncritical updates would have to call line Y, where the problem manager would pop over and provide updates. except guess what: the numbers never changed. so everyone would just call in to line X anyway and start making demands. on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

around the time i switched out of operations it had become standard for people working the issue to call in to line X on their desk line, then just call one another on personal cell phones to actually coordinate work. we'd get yelled at for doing so because 'everything is supposed to be open so nobody who might have a solution is left out'. didn't stop anyone.

Penguissimo posted:

post the number

Penguissimo posted:

post the number

Penguissimo posted:

post the number

Iridium posted:

oh poo poo that reminds me

in addition to my company's general conference line like the webex / skype poo poo, our phone system has several dedicated conference lines. no special access code is needed, it's for emergencies: if there's a massive outage, you can dial into just a basic phone number from anywhere at all and be on the bridge. they're not commonly used now (short of super severe network emergencies), but when i first joined the company and worked in operations it was the standard. each time we had a critical outage, they'd send out the alert and one of us would have to hop on.

but this got to being a problem because absolutely everyone could call in, and the number would spread very quickly. the people trying to work on the issue would be trying to coordinate and do poo poo, but the 'problem manager' would want constant updates, and demand that everyone stop talking to update whatever other random middle manager hopped on and demanded info. as you'd expect, this became a complete clusterfuck, so they tried to implement a rule saying that people working the issue would be on line X, while anyone needing noncritical updates would have to call line Y, where the problem manager would pop over and provide updates. except guess what: the numbers never changed. so everyone would just call in to line X anyway and start making demands. on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

around the time i switched out of operations it had become standard for people working the issue to call in to line X on their desk line, then just call one another on personal cell phones to actually coordinate work. we'd get yelled at for doing so because 'everything is supposed to be open so nobody who might have a solution is left out'. didn't stop anyone.

Iridium posted:

oh poo poo that reminds me

in addition to my company's general conference line like the webex / skype poo poo, our phone system has several dedicated conference lines. no special access code is needed, it's for emergencies: if there's a massive outage, you can dial into just a basic phone number from anywhere at all and be on the bridge. they're not commonly used now (short of super severe network emergencies), but when i first joined the company and worked in operations it was the standard. each time we had a critical outage, they'd send out the alert and one of us would have to hop on.

but this got to being a problem because absolutely everyone could call in, and the number would spread very quickly. the people trying to work on the issue would be trying to coordinate and do poo poo, but the 'problem manager' would want constant updates, and demand that everyone stop talking to update whatever other random middle manager hopped on and demanded info. as you'd expect, this became a complete clusterfuck, so they tried to implement a rule saying that people working the issue would be on line X, while anyone needing noncritical updates would have to call line Y, where the problem manager would pop over and provide updates. except guess what: the numbers never changed. so everyone would just call in to line X anyway and start making demands. on top of that, though, we discovered that in a few instances, former employees would call in for the hell of it now and then (there'd be something every day usually), with one that they discovered had been doing so for multiple years. a few managers freaked out but they didn't really have a way to stop him. he'd just sit and listen though so it's not like anyone cared.

around the time i switched out of operations it had become standard for people working the issue to call in to line X on their desk line, then just call one another on personal cell phones to actually coordinate work. we'd get yelled at for doing so because 'everything is supposed to be open so nobody who might have a solution is left out'. didn't stop anyone.

Rex-Goliath posted:

uncurable mlady posted:

how we can help them devops