Readit NewsWhat the article doesn't point out is that this is deeply ingrained not just among companies but among customers, too, and it's one of the many culture shocks I've seen my colleagues who move between US and EU markets experience.
If a European customer (adjusting for geographical variation, Europe is pretty big and diverse) runs into some weird issue and they call tech support, there's a very good chance that you've already lost them. It doesn't matter if tech support was super helpful, remedied things right away, and the customer support experience was top notch. The perception is that if they had tech support to un-break it, someone not only cut corners, but didn't even cut them very well, and now they wasted their time, too.
This isn't "just a cultural thing", it's ingrained because of how customers themselves do business, too (which makes it especially difficult to deal with in a B2B setting). The whole chain of commercial relations and norms is structured in such a way that depending on a "move fast and break things" platform is a very, very bad idea.
This is one of the most frequent things I had to explain in review meetings, and it went both ways:
- People who moved from US to EU markets didn't understand why customers had nothing but good words to say about customer support and then didn't renew contracts citing quality issues
- People who moved from EU to US markets going nuts over product release timelines getting aggressively slashed not so much because the feature sheet was too thin but because they thought there was no way to get those features tested enough
One thing the GNOME community got right, despite the clamour and gnashing of teeth.
Consistent cross-app theming support is a pipe dream from the 90s that has never worked, except in manicured screenshots to get karma points on /r/unixporn
KDE solved 99% of the theming requirements by just allowing color customisation and shipping with a default theme that doesn't suck too badly.
Pre-emptively, I'm not saying anything below applies in your case :-).
A mismatch in the threshold of "they should already both know and have internalized" is where much of the friction in high-stress organisations comes from.
I see a lot of people expecting, as the parent post put it, "a clear set of steps that can be burned down [to get to a good result]", but entirely oblivious to the fact that the people they expect it from:
1. Don't have the organisational authority to organise it -- they can do "their part" but they can't tell people on whose work they depend what to do.
2. Don't have access to the same task-specific information as the person who expects it of them, and don't know who to ask because teams are heavily compartmentalised and/or hierarchical.
3. Don't have access to the same kind of organisational information as the person who expects it of them.
Much like responsibility, deflecting blame comes from above. In my experience, what the parent poster says is true: people who are bad at what they do and try to make it someone else's problem is probably the most common source of stress. But it is also my experience that the middle leadership layers of companies where this is a chronic problem is almost entirely populated by managers who try to make everything other people's problem, and whose teams end up having to deflect everything by proxy whether they want it or not.
I think this is part of the nuance that's lacking in the parent post. It's very hard for someone to work significantly above their organisation's level.
Indeed the ones getting hacked are more likely to.
> user names and passwords for logging in to various accounts belonging to Schutt have been published at least four times since 2023 in logs from stealer malware.
So this isn't from website dumps with plaintext passwords.
Actually critisizing DOGE for their major gaffes (like putting up easily defaceable websites, or their incompetence when it comes to reading numbers accurately) is important, but this kind of article is just sad and diminishes the credibility of news journalism
If your password is in the dumps, too, like this person's passwords, then yeah, you might want to look into it.