You could possibly invent these things as a Turing machinist but it'd be by stumbling backwards into them and likely doing a shitty job.

e.g. pretty good for config files or basic serialization

midwit meme template

guy on left: katie u want meet 3pm discuss project

midwit: Hi Katie, I hope this message finds you well and that your week has been off to a productive start. I wanted to reach out and proactively touch base regarding an opportunity to align on some of the ongoing project-related workstream...

guy on right: katie u want meet 3pm discuss project

Being able to minimize boilerplate and have strong refactoring and bug resistant types is a huge edge.

The only problem is their ecosystems are limited so you might spend more time than you like implementing an API or binding a system library.

These commitments were commitments by the administration in the White House at that time. They were not accords or treaties ratified by Congress. Agree with them or don't, they should have been understood as what they were: limited in legitimacy and free to be canceled by the next administration with no discussion.

This isn't a matter of arcane political skullduggery, it's spelled out in the US Constitution's definition of treaty, Article II, Section 2, Clause 2. The people were not formally heard.

Here's where I would expect the CEOs of the other AI labs to stand by Anthropic and say no.

Polyamory still comes off as a low status behavior.

Karpathy is probably the most careful not to write off LLMs entirely but he seems pretty skeptical.

Untyped FP languages can be productive, flexible, even elegant (I guess) but they are structurally incapable of expressing large classes of correctness claims that typed FP makes routine.

That doesn’t make them useless, just, you know. Inferior.

The missing context whenever this comes up is the fact that it was a surprise one off.

If developers have no idea they're going to be graded by lines of code at some random future date that's a much different situation than saying you're going to give bonuses away every month based on how many lines of code were written.

Everyone knows the second is bad, it'll be gamed massively. The first one could be useful though.

And yes doing it as a one off is still problematic and you can think of all kinds of exceptions, but if you think the organization is full of dead weight in general and overhired massively, a crude stack ranking by lines of code is a pretty good metric for figuring out which (e.g.) 50% is the bottom.

It's true this was 4 months after AoC 2024 was out, so it may have been trained on the answer, but I think that's way too soon.

Day 3 in 2024 isn't a Math Olympiad tier problem or anything but it seems novel enough, and my prior experience with LLMs were that they were absolutely atrocious at assembler.

https://adventofcode.com/2024/day/3