Re:Programmer interrupted: The cost of interruption and cont...
by mangamadaiyan on Wednesday April 05, 2023 @08:43PM
(#35462590)
Heh. The same at my workplace, except that build times suck, tests take a long time to run (and are not dependable), and you're expected to be on an electronic leash -- namely, one of the worst possible instant messengers.
Re:Programmer interrupted: The cost of interruption and cont...
by steve1977 on Thursday April 06, 2023 @04:13AM
(#35465675)
You can say MS Teams here, it’s ok…
Re:Programmer interrupted: The cost of interruption and cont...
by JPws_Prntr_Fngr on Thursday April 06, 2023 @12:32PM
(#35470797)
I would rank Slack above Teams in nefariousness, because it's a better tool, so people like it more, use the shit out of it, and inundate you with so much more noise.
Re:Programmer interrupted: The cost of interruption and cont...
by mangamadaiyan on Thursday April 06, 2023 @12:49PM
(#35471040)
Touché :)
I find that this leads everyone to constantly do multiple concurrent tasks. After a long day I often have a headache from having to concentrate on both my coding task, an operations task, a meeting, and a new request at the same time.
Ultimately, as you would expect - productivity is awful. They then have lengthy discussions on how to improve productivity by every mechanism other than what’s known to work (faster builds, faster tests, increased focus time)