Quotes

When I speak in front of groups and ask them to raise their hands if they used the free version of ChatGPT, almost every hand goes up. When I ask the same group how many use GPT-4, almost no one raises their hand. I increasingly think the decision of OpenAI to make the “bad” AI free is causing people to miss why AI seems like such a huge deal to a minority of people that use advanced systems and elicits a shrug from everyone else.

Here, on the level sand, Between the sea and land, What shall I build or write Against the fall of night? Tell me of runes to grave That hold the bursting wave, Or bastions to design For longer date than mine. Shall it be Troy or Rome I fence against the foam, Or my own name, to stay When I depart for aye?

I am increasingly worried about AI in the video game space in general. [...] I'm not sure that the CEOs and the people making the decisions at these sorts of companies understand the difference between actual content and slop. [...] It's exactly the same cryolab, it's exactly the same robot factory place on all of these different planets. It's like there's so much to explore and nothing to find. [...] And what was in this contraband chest was a bunch of harvested organs. And I'm like, oh, wow. If this was an actual game that people cared about the making of, this would be something interesting - an interesting bit of environmental storytelling. [...] But it's not, because it's just a cold, heartless, procedurally generated slop. [...] Like, the point of having a giant open world to explore isn't the size of the world or the amount of stuff in it. It's that all of that stuff, however much there is, was made by someone for a reason.

Look at Sony, or Microsoft, or Google, or anyone. They still don't get it. They're still out there talking about chips, or features, or whatever. Or now they're all hot for design. But they think design means making pretty objects. It doesn't. It means making a system of pieces that all work together seamlessly. It's not about calling attention to the technology. It's about making the technology invisible.

Miss Wilson, when she was a resident superintendent in this Palace, had a cat that apparently caught up to 60 mice a night. The corpses were then swept up in the morning. Finally, does the noble Lord recognise the fire hazard that mice pose, because they eat through insulating cables? It would be a tragedy for this beautiful Palace to burn down for lack of a cat.

There is something so vulnerable and frightening about doing your own thing, because it’s your fault if it doesn’t work. And then there’s this other kind of work, where you’re paid an extraordinary amount of money, you’re the hero before you walk in the door, you’re not even held that accountable, because you have a limited amount of time, and all you can do is make it better.

My main concern is that the substantial cost to develop and run Al technology means that Al applications must solve extremely complex and important problems for enterprises to earn an appropriate return on investment. We estimate that the Al infrastructure buildout will cost over $1tn in the next several years alone, which includes spending on data centers, utilities, and applications. So, the crucial question is: What $1tn problem will Al solve? Replacing low-wage jobs with tremendously costly technology is basically the polar opposite of the prior technology transitions I've witnessed in my thirty years of closely following the tech industry.

When I was brought down from my prison to the Court of Bankruptcy, between two policemen,—waited in the long dreary corridor that, before the whole crowd, whom an action so sweet and simple hushed into silence, he might gravely raise his hat to me, as, handcuffed and with bowed head, I passed him by. Men have gone to heaven for smaller things than that.

Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then: -> layout elements -> rasterize them to a 2d screen -> diff that against the previous screen -> finally use the diff to generate ANSI sequences to draw We have a ~16ms frame budget so we have roughly ~5ms to go from the React scene graph to ANSI written.

[SQLite is] a database that in full-stack culture has been relegated to "unit test database mock" for about 15 years that is (1) surprisingly capable as a SQL engine, (2) the simplest SQL database to get your head around and manage, and (3) can embed directly in literally every application stack, which is especially interesting in latency-sensitive and globally-distributed applications. Reason (3) is clearly our ulterior motive here, so we're not disinterested: our model user deploys a full-stack app (Rails, Elixir, Express, whatever) in a bunch of regions around the world, hoping for sub-100ms responses for users in most places around the world. Even within a single data center, repeated queries to SQL servers can blow that budget. Running an in-process SQL server neatly addresses it.

Old technologies that have stuck around are sharks, not dinosaurs. They solve problems so well that they have survived the rapid changes that occur constantly in the technology world. Don’t bet against these technologies, and replace them only if you have a very good reason. These tools won’t be flashy, and they won’t be exciting, but they will get the job done without a lot of sleepless nights.

Today, Facebook counts 29% of its employees (and growing!) as Hive users. More than half (51%) of those users are outside of Engineering. They come from distinct groups like User Operations, Sales, Human Resources, and Finance. Many of them had never used a database before working here. Thanks to Hive, they are now all data ninjas who are able to move fast and make great decisions with data.

[On WebGPU in Firefox] There is a _lot_ of work to do still to make sure we comply with the spec. in a way that's acceptable to ship in a browser. We're 90% of the way there in terms of functionality, but the last 10% of fixing up spec. changes in the last few years + being significantly more resourced-constrained (we have 3 full-time folks, Chrome has/had an order of magnitude more humans working on WebGPU) means we've got our work cut out for us. We're hoping to ship sometime in the next year, but I won't make promises here.

The hard part of computer programming isn't expressing what we want the machine to do in code. The hard part is turning human thinking -- with all its wooliness and ambiguity and contradictions -- into computational thinking that is logically precise and unambiguous, and that can then be expressed formally in the syntax of a programming language. That was the hard part when programmers were punching holes in cards. It was the hard part when they were typing COBOL code. It was the hard part when they were bringing Visual Basic GUIs to life (presumably to track the killer's IP address). And it's the hard part when they're prompting language models to predict plausible-looking Python. The hard part has always been – and likely will continue to be for many years to come – knowing exactly what to ask for.

Having worked inside AWS I can tell you one big reason [that they don't describe their internals] is the attitude/fear that anything we put in out public docs may end up getting relied on by customers. If customers rely on the implementation to work in a specific way, then changing that detail requires a LOT more work to prevent breaking customer's workloads. If it is even possible at that point.

I have seen the extremely restrictive off-boarding agreement that contains nondisclosure and non-disparagement provisions former OpenAI employees are subject to. It forbids them, for the rest of their lives, from criticizing their former employer. Even acknowledging that the NDA exists is a violation of it. If a departing employee declines to sign the document, or if they violate it, they can lose all vested equity they earned during their time at the company, which is likely worth millions of dollars.

It is a laborious madness and an impoverishing one, the madness of composing vast books—setting out in 500 pages an idea that can be perfectly related orally in 5 minutes. The better way to go about it is to pretend that these books already exist, and offer a summary, a commentary on them.

While we encourage people to use AI systems during their role to help them work faster and more effectively, please do not use AI assistants during the application process. We want to understand your personal interest in Anthropic without mediation through an AI system, and we also want to evaluate your non-AI-assisted communication skills. Please indicate 'Yes' if you have read and agree. Why do you want to work at Anthropic? (We value this response highly - great answers are often 200-400 words.)

One day, Korzybski was giving a lecture to a group of students, and he interrupted the lesson suddenly in order to retrieve a packet of biscuits, wrapped in white paper, from his briefcase. He muttered that he just had to eat something, and he asked the students on the seats in the front row, if they would also like a biscuit. A few students took a biscuit. "Nice biscuit, don't you think", said Korzybski, while he took a 2nd one. The students were chewing vigorously. Then he tore the white paper from the biscuits, in order to reveal the original packaging. On it was a big picture of a dog's head and the words "Dog Cookies." The students looked at the package, and were shocked. Two of them wanted to vomit, put their hands in front of their mouths, and ran out of the lecture hall to the toilet. "You see", Korzybski remarked, "I have just demonstrated that people don't just eat food, but also words, and that the taste of the former is often outdone by the taste of the latter."

Most journalists have grown up with a fortress mindset. They have lived and worked in proud institutions with thick walls. Their daily knightly task has been simple: to battle journalists from other fortresses. But the fortresses are crumbling and courtly jousts with fellow journalists are no longer impressing the crowds.

But the bearded bloke had shot his bolt. He stood there, licked at last; and, watching him closely, I could see that he was now at the crossroads...It was a dashed tricky thing, of course, to have to decide on the spur of the moment. I was reading in the paper the other day about those birds who are trying to split the atom, the nub being that they haven’t the foggiest as to what will happen if they do. It may be all right. On the other hand, it may not be all right. And pretty silly a chap would feel, no doubt, if, having split the atom, he suddenly found the house going up in smoke and himself torn limb from limb.