There has been a lot of discussion about negative emissions technologies (NETs) lately. While we need to be skeptical of assumed planetary-scale engineering and wary of moral hazard, we also need much greater RD&D funding to keep our options open. A quick thread: 1/10

Google's interview system is not great but there are various reasons why it feels less than it is. Most candidates don't know what the goal of our interviews are. First rule, it is not about finding an optimal solution or any solution at all.

You are interviewed for multiple skills simultaneously. Cognitive skills, communication, leadership are a few to name. If the point is not finding a solution, then what is it? Let me explain.

Your interviewers try to understand what it feels like to work with you on a daily basis. An interview question is just a tool in achieving that, it is not there to specifically measure your skills on a topic but a tool to understand the depth of your thinking.

Before the interview starts, ask them what they want to get out of this interview. Good interviewers should already have a plan and a set of expectations. Ask them what you should do. Don't start coding yet. Ask them you should produce. Discussion, diagrams, pseudo code, code?

Then, start cracking the question. List whatever questions you think it is important to solve this question, ask your edge cases. Get to a point where you are discussing about pros/cons of the solutions. These steps are critical. Don't just start coding. Have a consensus first.

it's done.

a visual enigma machine simulator: https://t.co/eLE4Sb97HW

you know how Atari called the Jaguar as a "64bit system", because it had two 32bit CPUs? (or because it had a 64bit bus, but let's not worry about that)
we should apply that logic to the current generation of consoles.
So the Switch is a 256bit console. It's the Nintendo 256.

The Xbox Series X? terrible name.
Better call it the "Xbox 512 Blu-ray".
like the Jaguar CD, the Sega CD... the good old days when consoles had their media type in the name.

Boringly the PS5 is also a Playstation 512 Blu-ray, because both of them are using the same AMD Zen 2 CPU.

The Switch one is weeeird. It's built on an Nvidia Tegra X1, which is an 8 core 64-bit CPU, so that should be 512, right?

Well... no. Four of them can't be used. And later documentation doesn't even mention them.

it's some weird system where the system-on-a-chip has four Cortex-A57 cores and four Cortex-A53 cores but only the A57s are usable?

I’m quoted in this, which does about as good a job overviewing the topic as a New York Times profile can be expected to.

Major oversights in it as I see.

First, It does not acknowledge the fact that Yudkowsky is, at heart, a complete crank. This remains, to my mind, crucial to understanding the rationalist community’s influence on the world: they’re sci-fi writers being mistaken for scientists.

You can’t really understand the harmful effects of SSC until you realize that it’s part of a larger movement of bullshit artists serving as cult leaders to the techbros.

Second, and more importantly, it never really explains the harm that’s being done by Scott Siskind and his followers. It comes close, noting that “SJWs” were the only group not welcome in SSC, but it doesn’t capture the harm of that because it doesn’t unpack the term.

What is meant in practice when “SJWs” aren’t welcome in a space is that marginalized people speaking of the harm they experience are silenced.

That’s it. That’s the meaning.

When you complain about an open source project's management you'll get the reply, "Use something else if you don't like it!" That'd be true except for the tiny problem that *many* projects also strive for complete monopolistic dominance.

Let me tell you about Java in early 2k:

I was programming in Java since it's release, and all through the late 90s into the early 2000s. At first Java was very determined to unseat C++ and it used various propaganda tactics to turn C++ and malloc into a weird enemy for all of us to hate. This worked great!

Everything was fine though because there were plenty of jobs in tech because of the dot-com boom, and then suddenly there were not jobs because of the dot-com bomb.

Overnight it seemed as if the *only* way to get a job was at giant companies, and they *loved* Enterprise Java.

Now, this is the golden ticket for many open source projects and corporations. They all want to be the top dog #1 in the industry for their particular use, and once they gain that position they become abusive by ignoring user needs and extracting wealth from them.

With Java the dominance was so insane that *every* language had to copy Java's weirdness to survive. If you wonder why a language has some odd CamelCase things it's because early Python, Ruby, and others had to copy Java's semantics and style to even be considered "serious".