>Colleagues, ex-colleagues, friends, family, everyone. The few who I have talked to that still want an office, have been in leadership positions, and usually this is from those who are higher up in the ranks.
That's the problem with looking at a limited number of opinions, I've seen a different consensus in people I've spoken to. Only 1 person (out of around 30) expressed a desire to remain completely remote and never go back to the office, while the rest favoured a hybrid approach. None of those I talked to (including a couple in the C-suite) expressed a desire to return to the office full-time.
Both things are bad and deserving of complaint. People have the capacity to be concerned about the bad working practices in both NYC and China at the same time, it's not an either-or situation.
You said Effective Python is one of the books you'd recommend to "every developer," are the topics covered broadly applicable rather than tied to language features specific to Python?
You missed the point. The idea of coordinating games between 60 trusted people is ridiculous. Anti-cheat and matchmaking between untrusted players is essential in modern (FPS) gaming.
Active moderation is still a thing now, people are just actively employed by the game companies to do that job. The cheating situation in multiplayer FPSs is generally much better now than it was back in the day I was a mod for CS:S servers.
That completely destroys a whole class of games. How do you suggest I get 60 of my friends together at once for a game of Apex Legends?
You'll never completely stop people cheating, but that doesn't mean that game developers should just give up. Thankfully the people clamouring for less, rather than more, anticheat is relegated to a vocal minority.
>But given that they want to go from Mongo to a graph DB, the fear is that this is someone who is only chasing the next cool technology and not solving an underlying business problem.
To be fair to the teach lead, I do feel like it was the other way around. MongoDB was foisted on us on a new project (we were previously SQL) by a software architect who left soon after. I've never felt that MongoDB was a good fit for what we want to do, but I want to return to SQL.
Is the latter not the case? I'm genuinely asking here, as this is a point of view expressed by my tech lead (though in our case it's a graph DB vs an existing MongoDB setup).
>They're deliberately trying to get people to take on debt rather than just do card payments
So what? It's 0% interest. It's incredibly helpful to have easy-access financing to split purchases across a few months.
>even simple things like buying a book through a web site requires declining several offers for paying with credit.
This sounds so specific it seems like you're taking a bad experience with one website and pretending all websites are like this. Most e-commerce sites I've used in the past year offer Klarna or some similar service and all of them have been implemented as just another option in a set of radio buttons.
The idea that they have been "bypassed" is indeed a fabrication. That phrasing implies that long-term studies are usually carried out in vaccine trials and an exception was made for COVID-19 vaccines. That is not the case. Long-term studies are always carried out after a vaccine has already hit the market.
It would be correct to say that no long-term studies have taken place, not that they have been "bypassed."