Increeedible. Just sheer chaos. 20 direct reports *AND* spend half your time writing code? Not possible.

FWIW, I always figured "Blue will have only half the ads of non-subscribers!" meant that he was planning on doubling the ads on the rest of us, not halving on others.

https://twitter.com/ZoeSchiffer/status/1589804893900263424

For a little under a year, I ran the OS group in a VPN appliance startup acquired by Nokia. I had to manage down, up, sideways and out:

Ah, Sabine, Sabine, Sabine...sigh. All right, I'm trying not to waste time on this, but:

My opinion of the video itself and how I would respond to a sincere, good-faith critique of the field are two very different things.

I don't have any inside knowledge, but here are the kinds of people that might have been lost: 1/

https://twitter.com/jredmond/status/1588675418064039937

The guy who knows which NIC brand fails under high loads, and so doesn't buy those even though they are cheaper.

@skdh @earltcampbell You are asking for several hours of my time.
Okay, I really had other plans for this morning, including prepping to talk to a potential funding agency this afternoon, but here goes...
Let's talk #QuantumComputer architecture, broadly. @skdh @earltcampbell Let's divide the scalability problem into four areas:
1. architecture-aware compilation of realistic algorithms, including
resource analysis and error correction (QEC)
2. architecture of large-scale quantum computers, including QEC
3. classical control systems
4. NISQy business

@earltcampbell @skdh I would not have picked "debunk" and "hatchet job", but I think Earl's piece here is calm and reasoned. Thanks, Earl.
As I said in another branch of this thread (we should create one decent summary), a lot of people have looked at the architecture problems in the last 15 years. @earltcampbell @skdh Sabine, you said you like to read the papers and summarize what you learn (as do I), here are a few names. Most of us have Google Scholar pages or are otherwise easy to find.
1/