this post was submitted on 26 Jan 2026
433 points (98.2% liked)
memes
19183 readers
3402 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sometimes Google seems so obsessed with open standards that they not only don't favor their other projects, their projects often simply won't support each other.
I blame the many Google buzz plus chat clients. Google also suffers from a lot of success, they can be complacent about things other companies obsess about.
My guess is that the Google org culture breeds people who don't care about the users of their tech one bit.
Make something that's fun and interesting for the person making it, release, get promoted, abandon.
It's the kind of people I tend to avoid hiring, and for a good reason. Google makes pretty much all its money from search ads, and hasn't innovated on that in decades.
That they don't care wouldn't be my take, but it may be true for some.
It is true it is hard to get the incentives right, especially if your goal is to make things that don't get abandoned.
They do a lot of experimentation though, trying to see what works.
I think "what works" and "what users want" are two similar, intersecting but not at all identical sets. Some users like new and broken, others want things that will never work.
I am curious what kind of people do you try to hire, and what do you screen for? I mainly just try to gauge someone's experience in the field, and ability to to fit a specific role. (I have mostly been involved in Android app dev or related interviews).
I ask things like "how do you solve this common problem". A goal for me is to try to give basically the same interview over and over again, to make it easier to compare candidates. But over the years it changes of course.