563
I know nothing about computers but this does not add up
(reddthat.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Aug 2025
563 points (100.0% liked)
memes
17022 readers
2812 users here now
Community rules
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
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
This is MS we're talking about. Preview and Viewer are probably made by two different teams in different countries, sharing no code, and prohibited from communicating with each other, even if they know about the other's existence.
And famously they fired all QAs years ago so there's nobody to test before releasing.
I work in big tech and this is my life. I envy anyone who thinks you're exaggerating, because that means they haven't experienced the joy of spending weeks trying to track down the team responsible for a bug and then months hassling them to fix it.
And if they do talk to each other, the different departments need to go through the whole hierarchy for everything and each manager puts their spin on it, so you get answers back from questions that were not asked.
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.
Wait does this mean I work in little tech?
Little tech? Like, a micro company that makes software? A "micro-soft", if you will.
No no, it needs to be more present, more ubiquitous, more "ubi-soft"
One leveraging the graphics engine from internet explorer the other using the graphics engine from ms paint 1.0
I imagine the two teams sharing the same desk through a hole in the wall like in Brazil.
I can almost guarantee that they would be using different things. usually you have simpler libraries to decode formats (almost 1 for each codec), and separate programs plug these libraries in to generate the output. previews do not have to be accurate and have to be fast, so a simpler program with just linear scaling or something, where as actual image would be complex which has to worry about accuracy.
still not a excuse to not have support for a free 15 year old format