It almost looks like a Rust syntax to me, which is only one way to do that. A concise syntax is always possible if that's prioritized, like `(ctx.get(thing)? == Thing.A) ?? false` or `ctx.get(thing)?.(_ == Thing.A)`. Actual Rust programmers would also prefer to check against the explicit value whenever possible: `thing == Some(Thing.A)`.
Yes, language design should cater to people who have spent a little bit of time using and learning it, because they represent the majority of hours spent using that language. What a language looks like to someone who's never seen it is sort of irrelevant. That code could also have been written more imperatively, and probably would be by many people for those who don't like the functional style.
Who's the bigger problem, the idiot yelling fire in the crowded movie theater, or the morally superior intellectual supporting their right to do so? I'm not so sure.
> Where WFH falls short is building alignment on larger initiatives, and that's what we're seeing.
Where are we seeing this? I'm a manager at a mostly WFH company and we don't fall short on this.
Big thing is this was never an office based company, WFH is in the DNA from the co-founders and while we regroup occasionally, remoteness has not affected our ability to grow and build meaningful things. One could argue that we might do better if we were an office based company but as far as I know there's no data out there showing that this would be the case.
Eons ago now (circa 2009/2010 I think), when working on Pornhub we switched from memcached to Redis for a few reasons:
- memcache had little to no observability, it made debugging cache issues a nightmare. Redis on the other hand is a dream to work with on that front, from the cli that is well thought out to the fact you can copy the db file to your machine and go at it, it's just a much better developer experience.
- Data structures, Redis' lists, hashes and sets meant we could represent a lot of a stuff as is in cache with no need for costly serializing. It also meant the data layer code was simpler than the memcached equivalent.
- Built in pub/sub, we used it for tons of stuff and the fact it came built in was big as prior to that we had to provision specific stacks to get the same functionality (and it wasn't has nice to use.
memcache has its use but for the little advantages it gave (perf wise) Redis just buried it in developer experience.
The author is French, the usage of quitted is more likely a mistake outright. As for the quoted version it's explained next to it, he's quitting professionally but likely will continue as a hobby, in French you'd use quotes to highlight the fact it's not to be taken literally.
"To quit" is an irregular verb in English, the past tense is just quit instead of quitted. So "I quit" can be either present or past tense, but from context it would be clear that "I quit infosec" is past tense.
It's an engine written in C++ (not Unreal) that we've added C# scripting to. So it's in the same kind of situation as Unity where their engine calls from C# land need to be marshaled into calls to native code and back, which of course has overhead.
If they have data, share it, in the absence of said data we can only assume it's poppycock. Exec teams do that all the time, work on feel, why should we believe it's any different here?
> The CEO of Amazon doesn't make a decision of this magnitude based on a whim. They'll have mountains of productivity data on remote work by now and it even says so in the post.
If it says so it must be true. There's no data in that post, just platitudes management like to use about collaboration and creativity that is absolute BS.
Shame I left the company I was at during the pandemic because I could dig the data but there was a very clear 20% sustained benefit in terms of productivity when WFH: faster to close tickets, bigger releases, less bugs. Did culture suffer? Yes. Did it matter, no, because culture is some vague notion only HR and senior management cares about, or at least pretends to.
They still mandated RTO in the end, which cost them half of their more senior engineers, positions they still have not managed to fill, what a surprise when you want to force people through unproductive hoops.
I now work in a remote first company and in 16 years of career it's the most productive team I've been part of, shit gets done at all levels more so than in any other company I've been part of.
