555
I know nothing about computers but this does not add up
(reddthat.com)
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Here's a real and true story about how separate Microsoft teams communicate and coordinate:
Few weeks ago, some Microsoft team from the US deprecated some critical service used by other Microsoft products. They just shut it off without notifying anyone. Other teams from other Microsoft offices in the rest of the world found about this deprecation when their production builds started failing to log customers in to the applications that they need for their businesses. People were called in from their vacations, emergency meetings were held to play hot potato with responsibility. Clients were PISSED. I stopped following the drama before it was resolved.
What is actually the best way to set up good communication between people and departments? Daily stand-ups tend to become hour long meetings. Make it an e-mail means people don't read it half the time, some even having a rule to automatically shred that kind of mails. Set up talks between people and have a bunch of them not showing up but then get angry nobody asked them for their opinion.
For example a matrix org structure can do wonders.
Really, anything other than vertical hierarchical setup favored by so many tech companies.