> The sharp rise in both polarization and the number of close friends occurred between 2008 and 2010—precisely when social media platforms and smartphones first achieved widespread adoption. This technological shift may have fundamentally changed how people connect with each other, indirectly promoting polarization.
Indirectly? Seems to me that this is far more likely the "direct" cause, given what we know about the psychology around algorithmic feeds.
Also - I'm not sure if I missed it in the article, but did they define what they mean by "close relationship" means? I'd be very curious to know if a purely online relationship is counted and how this may also contribute to the observations made.
First of all, I'm sorry to hear you're dealing with a person like this. It reminds me of a guy who was on my previous team. Relatively competent. Stuck at Senior. Had a lot of issue seeing (often younger - myself included) engineers getting promoted to Staff, Principal, etc. over him. Knew that he had an incredibly toxic and abrasive personality and thought merits alone should allow him to move up the ranks. He would reign it in sometimes after people complained either to him or to the manager, but he'd go right back to his old ways a few days later. So. Frustrating.
Anyways, my advice is: document. Document specific instances of behavior that you see that is toxic or disruptive to the team.
It sounds like this person needs to go - or someone else needs to start addressing their behavior with them. Either scenario will require that person (your manager, skip level, or HR - or some combination) to have examples of specific instances of behavior that needs to be addressed.
Others have recommended the empathy approach. Talk to the guy. Take them out to lunch/drinks/whatever. If you haven't tried it at least once, I agree it's worth trying. There's always a chance your reading things wrong or don't have the whole picture. But if you have tried kindness and understanding, and things don't change or they only change temporarily... I don't think the "kill them with kindness" approach will work in this case. It's the approach I tried in my situation and all it did was drain me and take away all of my excitement to work on the project he worked on. Because this person will never change and you can't make them change.
Whenever I've been around toxic people like this, I always use the "if everyone's a jerk, you're the jerk" heuristic. Because I certainly can lose my cool and be a jerk sometimes. Not always intended. So in order to ground myself, I ask: OK... who do I have problems with? Just one person? THAT person? Yeah. Anyone else? No... everyone else is pretty awesome! OK... what about them, have they expressed they have problems with more than just me? All but one person on the team!? Huh. Yeah... That seems off. It's far more likely they're the jerk.
Certainly not a hard and fast rule. But it's helped me stay sane through abusive relationships both professionally and personally.
Last point - unless this person reports directly to you, they're not your responsibility to fix. If you've talked with them and expressed frustration with the _behavior_ you're observing, you've already done your part. Your management needs to step up. If they disagree with the state of reality, then figure out why there's a disconnect. That's where documentation is your friend! If you can convince another coworker to do the same and they also can provide documentation that corroborates or supplements, even better. I wouldn't be too afraid of being clear to your manager that this is something that you need fixed in order to feel comfortable and productive at work. It doesn't need to be "it's me or him". Make it about how _you_ need help from your manager. If you can show them that effort has been made on your own to address the situation and it's not working, then any competent manager should work with you both to find some sort of path out of this. If they continue to refuse (especially if multiple team members are expressing the same thing) then I would consider escalating to your skip level and then to HR. Chances are, assuming this person really is a jerk, that these people are already aware of what's going on. If no one seems to care that a bad personality is dragging the team down, then that's a huge red flag on the company culture as a whole and I would gtfo as quickly as I could line a new job up.
Good luck. I hope you can find some relief here. Life is too short to put up with other people's crap.
> I believe this is actually the entire point of Windows' volume shadow service (which is sort of poo-pooed in the article), to enable applications to tell the snapshot mechanism "wait, I'm in the middle of a file system transaction" and then to pause writes until the snapshot operation occurs after they finish the in process transaction.
Former maintainer of VSS here. Yes, that's exactly right. In fact, filesystem snapshots are usually not enough for true application level consistency. As others have noted elsewhere, a filesystem snapshot is the equivalent to yanking the power cord out of the back of your computer. It's good, assuming your filesystem does atomic writes / copy-on-write / write-to-new. But we can do even better.
Imagine I have two databases - one traditional relational DB storing my app content, and a second log database. You want to keep these in sync. Well, good luck doing this with the filesystem alone. Usually your DBMS will need to be involved as well, and this is where the VSS "writer" concept comes in. When a snapshot is being taken, applications such as SQL will be invited to participate. Typically, this means they'll start to hold up writes so that things will be quieter for the snapshot. But they will also have a chance, after the fact, and to actually clean up the snapshot itself. In this case, the DBMS could roll back the log database to then match the content database.
It's correct that NTFS doesn't support snapshots natively, but Windows has the volsnap.sys driver that takes care of it. For all intents and purposes, NTFS does support copy-on-write snapshots.
Complicated? Sure. But it was quite capable, and actually a pretty cool (but sadly under appreciated) piece of technology.