That's not the claim. The claim is that we don't know if X is possible under Swiss law. You seem to be the one claiming that because they said it's not possible, then it's not possible. If not, I don't know what you're claiming.
The GP says that it's possible under German law. Is it "FUD" to say that it could end up being possible under Swiss law?
Shouldn't there be fear, uncertainty, and doubt about any channel that activists use to communicate with each other?
>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.
The surveys I've seen have been pretty consistent (for people who can work from home most days): about 20% fully remote and about 20% five days per week in office with the balance coming in a few days per week. I see a pretty broad consensus that hybrid will be the main mode although mostly in office and fully remote will be significant too.
One challenge is that this means that in-office people that were used to everyone being physically present will largely have to adapt for many meetings (for example) to operate as if everyone were remote.
I'm not sure what you can judge from right now. I'm familiar with companies that are allowing people back in offices if they want and some people are going in but it's not the default. Apparently it's pretty dead so you basically go in and work. But I don't really expect that to be the norm, say, next year.
It is dead, because nearly no one wants to come in given choice. We could agree on whole team coming in and we discussed it a bit. Initially half our team came for few days and then it gradually dropped. Convenience of being at home won.
Some people do want basically a co-working space that isn't their house/studio apartment. But, for a lot of people, even an "OK" commute that lands them at a desk near maybe one or two people they work with, possibly in a hoteling arrangement, isn't really that attractive. And, with underutilized offices, amenities--such as they are--are going to get pulled back as well.
What you're ending up with is that neither the people who want to be remote nor the people who were OK with going in specifically for pre-pandemic office are interested in going in. I'm not sure how well hybrid works and there will probably be some shifting around as a result.
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?
I think it's more that I've met so few developers who don't end up using Python in any form (scripting or actual application development). So if you never actually do anything in Python then sure it's not going to be relevant.
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.
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.
When one of your 60 friends refuses to stop cheating, maybe stop inviting him to the party. Lots of games and lots of circles of gaming friends get on just fine without kernel-mode anti-cheat.
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.
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).
Absolutely unrelated. You can think of GraphQL as a standardized glorified RPC that calls arbitrary functions that return some data. Whether the source of data is an RDBMS, a bunch of REST microservices, DynamoDB, redis, SQLite, a flat JSON file, Neo4j, or a D12 dice doesn't really matter.
The "graph" part is if your arbitrary data is actually somehow related, you can traverse those relationships in one request instead of having to do many calls in a waterfall.
Not especially, no. It likes trees, or things that can easily and naturally be represented as trees, best, as far as I've ever been able to tell. Granted, I suppose, that's a kind of graph.
