616 karma · joined May 31, 2018
As soon as player-vs-player is introduced, f2p players become part of the "experience" for the whale players.
Edit: I might have misunderstood parent, who might be referring to Podman attempting to manage the uid mapping.
But at least the metric system tries to be consistent -- different units can be related and convert in a systematic way.
Cert seems to have expired two days ago.
Unfortunately they don't work on GitHub Pages yet. I still have to resort to GitHub Actions to invoke a container to render my RMarkdowns into a GitHub Pages branch --- wish one day I can retire that pipeline.
Not to mention downloading and parsing 20mb-worth of html+js each time you open up the wiki can be quite slow.
As for lazy loading --- when enabled, it breaks the indexing (e.g. finding backlinks) and searching because these are done by the js inside the browser too. I only lazy-load images and binaries because they are not indexable anyway.
Yep. Graphs are not "scalable" unless the visual elements are meaningful in themselves; they are mostly for "feeling-good-about-oneself" --- "look at all the notes I took and linked!".
Influence can propagate so easily through mass media, meaning that it is now possible to generate enough business interest just through "hyping" (it's difficult to achieve this when messages have limited reach) --- combined with the fact that it is often cheaper and less risky to "talk" than to actually "do", we end up with a culture where hyping is preferred whenever possible.
Of course, in the real world no IQ test is ideal.
Critics of the tech interview are certainly not against the merit-based selection --- it's more like the 1.5x engineers fear that the standardised interviews are being abused to allow 1x engineers who are "just-in-for-the-money" to appear as 2x, making their lives harder.
Meanwhile, 10x engineers probably are not bothered by this at all since 2x isn't enough of a threat.
"Get-to-know-each-other" type of interviews are nice, but it's rather inefficient when a job posting receives hundreds of applications.
As such, puzzle-based interviews are optimised to reject candidates who are not smart enough and have either not bothered to play the interview game or those who don't have what it takes to learn to play the game.
Not quite --- "preparing for the test" is also known as "studying".
You were probably thinking of IQ tests.
I very much agree. I feel there has been a trend recently where people (re)discovered how cool and useful ASTs are and now expect everything be using them. I suspect old-school computer scientists might be secretly laughing at this while programming with some Lisp-like languages they invented for themselves.
Jokes aside, I do wonder how modern IDEs manage to parse broken source code into usable ASTs --- is this trivial (CS theory-wise) or are there a lot of engineering secret sauce involved to make it work?