5 ms·

Or, you know, humans could just get their shit together and use asynchronous communication channels in the first place. Using AI for this is like a trying to s

Or, you know, humans could just get their shit together and use asynchronous communication channels in the first place. Using AI for this is like a trying to solve a self-created problem. If human meeting culture would have just used an issue tracker and e.g. emails for this, this all would not have been necessary. Human meeting culture exists only because the tools for synchronizing states is so bad in its UX/UI that there is seemingly no better way to do it. If Teams would have had a better UX focussed on issue management combined with better overviews for different roles, they would not have needed AI bots/avatars for this problem.

lloeki 2y ago
Although due to Poe's law I'm unsure if GP was earnest, I elected to read it with a /s modifier.
- stego-tech 2y ago
  Same here, because otherwise I’m afraid the disease has reached their brain, and they must be destroyed. /s In all seriousness, I hope that was sarcasm, because otherwise that sounds like absolute hell and the biggest waste of resources since the performance review. Except instead of just wasting time, now it also wastes energy, fresh water, land, and rare earths too.
xattt 2y ago
To add to this, anti-social assholes who kill team jive tend to hide from responsibility with e-mails. Even when it needs to be a meeting. They need to be dragged out of their comfort zone kicking-and-screaming for public display for the pleasure of others.
georgeplusplus 2y ago
In my organization the tools are great but the people don't put the work in to use them correctly. They rely on meetings and emails to get up to date information when the information can be captured on a ticketing system. My organization is very beaurocratic and has an older age group though.
tetha 2y ago
Some of the best architectural work we've done at the company was implemented more like a research paper. Have a central document, write down the current knowledge about an outage, or the current proposal - and improve on that through comments, revisions and discussion. And then you can still have a meeting or a call if a non-obvious decision needs to be made, or if clarification and explanation of something is needed.

lloeki 2y ago

Although due to Poe's law I'm unsure if GP was earnest, I elected to read it with a /s modifier.

stego-tech 2y ago
Same here, because otherwise I’m afraid the disease has reached their brain, and they must be destroyed. /s In all seriousness, I hope that was sarcasm, because otherwise that sounds like absolute hell and the biggest waste of resources since the performance review. Except instead of just wasting time, now it also wastes energy, fresh water, land, and rare earths too.

xattt 2y ago

To add to this, anti-social assholes who kill team jive tend to hide from responsibility with e-mails. Even when it needs to be a meeting. They need to be dragged out of their comfort zone kicking-and-screaming for public display for the pleasure of others.

georgeplusplus 2y ago

In my organization the tools are great but the people don't put the work in to use them correctly. They rely on meetings and emails to get up to date information when the information can be captured on a ticketing system. My organization is very beaurocratic and has an older age group though.

tetha 2y ago

Some of the best architectural work we've done at the company was implemented more like a research paper. Have a central document, write down the current knowledge about an outage, or the current proposal - and improve on that through comments, revisions and discussion. And then you can still have a meeting or a call if a non-obvious decision needs to be made, or if clarification and explanation of something is needed.