Dan Harper (@DanHarper7) header
Dan Harper (@DanHarper7) profile picture

Senior Staff Software Engineer @meta, words are my own.

London, England
Joined April 2008
Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)Photo by Dan Harper (@DanHarper7)
First day at @facebook 😀
4
1
51
Dan Harper retweeted
If you’re not reading the code, whether explicitly or through agentic inquiry, one or more of these is true: ○ You’re a beginner ○ Software is throwaway ○ You’re prototyping ○ You have no users / revenue ○ You’re taking on debt & risk ○ Your problems are basic And btw. All of this is fine. But the reality is that models are still not at the “full autonomy” stage yet. They make rookie mistakes, they go down bad architectural paths. I just had the best model in the world add a nonsensical 700ms delay to “settle” something and it told me “you’re right, I was cargo-culting” 🤨 I am on the camp that this need will diminish more and more. Most code is indeed going to be assembly-like. But we also have the global internet and software infrastructure riding on these models and narrative, and we have to respect that.
571
768
324
8,330
1,328,738
Dan Harper retweeted
“we sandboxed the agent” meanwhile the agent:
175
1,927
138
25,954
684,931
Dan Harper retweeted
if you've been using latest frontier LLMs, it's almost certain that you would have noticed by now the newer models have become worse to talk to they're more robotic, they speak jargons, they spits out verbose text, and do stuff you didn't ask for how did that happen? well, i'm not the person who trained those models so i can't speak for certain, but i've known enough evidence that gives me a well-educated guess, and i thought it's interesting to share as a crash course of modern LLM training pipelines so here we go let's wind back to 2020. GPT-2 and GPT-3 already came out and were widely available, but they could only predict one token at a time - that's what LLMs are at their core token prediction was offered via API, but there was nothing you could "talk to". so while it generated a lot of excitement in the academic field due to the emergent intelligence, it didn't have any wide adoption in 2022, ChatGPT changed all that. the research work that led to ChatGPT was a model initially named "InstructGPT". it took GPT-3 as the intelligent base, and used reinforcement learning with human feedback (RLHF) to teach the models how to "chat" the core idea of RLHF is that you ask the model to generate a few responses, and then let real humans pick which one they like. do this over and over again, and you get a model that knows how to talk worth noting even as early as InstructGPT, research found that making the model more pleasant to talk to will reduce their pure academic capabilities. this was called "alignment tax", which is an interesting thing we'll come back to in a bit there were various techniques done to minimize the reliance on humans, but ultimately the reward is modeled after human preference, making these AI assistants easy to talk to so remember this: RLHF = training the model to be likable by humans in 2024, there was an inflection point introduced by claude sonnet 3.5 which was the first model that can kind of autonomously finish coding tasks. it led to the first wave of viable "coding agents" the way sonnet 3.5 achieved this was by training the model with a harness (now it's called an agent) that has bash and file editing tools, throw the agent into a virtual machine, give it a task, and let it try to complete it. these tasks all have a machine-verifiable outcome predefined, mostly via test cases, that can validate whether the model really finished the task or not then you let the model do billions and billions of attempts in such virtual environments, and some of them would succeed by chance. you keep the successful agent sessions, and use reinforcement learning to teach the model to do that more, and boom - you get a coding agent that is called reinforcement learning with verifiable rewards (RLVR). if you look closely, you'll see that in this RLVR process, the final text response from the model doesn't matter AT ALL, as long as the code written by the agent could pass the test. it could talk like a jerk and it would still be rewarded so remember this: RLVR = training the model to be accepted by machines late 2024 and early 2025, we saw o1 and deepseek R1 came out as the first wave of "reasoning models". this article is getting long so i'm not diving into reasoning models now, but just know that reasoning models also relied heavily on RLVR to scale the training process - let the model think before taking action, and if the thinking led to a machine verifiable outcome, reward the thinking trace and teach the model to think like that more often the biggest difference between RLVR and RLHF is that RLVR is more scalable. human feedback is expensive to get, especially in domains where only an expert can have a valid opinion on which result is good with RLHF, if we let the model generate 100 responses, then a human has to review all 100 responses to pick which is good with RLVR, the human (or sometimes an AI) would define a task and verifier only once, and the model can generate a million responses - the machine verifier will pick which responses are good in an automated way so as a result, RLVR is becoming more and more dominant in newer models' training pipeline if you put all these things together: - RLHF = training the model to be likable by humans - RLVR = training the model to be accepted by machines - RLVR is more scalable - "alignment tax" says "likable by humans" makes the model do worse on verifiable tasks now you see why the newer models are becoming less and less likable? this is not just a "frontier labs screwed up their model training" problem - this is a war between machines and humanity, and humanity is losing we chased after benchmarks, when none of the benchmarks measure whether humans actually enjoy working with the model we use machines to decide which AI response is better because that's easier and cheaper, when we have no way of making sure those machines actually represent what we humans want we let AI go dark in a virtual environment on its own and complete predefined tasks at all costs, when in reality we often cannot define a verifiable outcome upfront, and need AI to work with us along the way i don't have a good solution to this, but i want to call for awareness that we're starting to witness a failure in aligning super intelligence right in front of our eyes this war between machines vs humanity is one we really can't afford to lose
236
332
133
2,970
294,410
Dan Harper retweeted
We're starting to leave the territory where you'd test an LLM by e.g. "create an svg of pelican on a bicycle". As one idea to generalize it, I was interested what Opus 5 would do if I gave it the first paragraph of the Lord of the Rings, a 1M token budget (~$10) and asked for three js render of it. Opus went off for ~2 hours and wrote 5500 lines of code that (procedurally) rendered the story. It's kind of janky but fun. But it's a bit mindboggling that the LLM has to place and orchestrate various polygon assets in (x,y,z) coordinates and write code that animates it all, and that it even does anything at all. I also like this kind of examples because no one in their right mind would ever spend the time to write something this custom but LLMs have all the stamina and patience in the world, so it's an example where we go from "no one would ever do this" to "sure, why not, it's ~free". There might be a lot more. But I'm excited about creating hyper custom worlds that you can imagine dropping players into, e.g. here to participate in the LoTR story as a spectator NPC, or one of the characters, or etc. Something like an ephemeral GTA of X on demand. Last thought is that the domain of worlds/games exposes a weakness in LLMs: they can't easily audit their work because they aren't able to efficiently and natively perceive videos or play games within them. Here, Opus 5 had to very slowly and painstakingly take screenshots at different points, and it messed up a few times and created a bunch of jank. An example of raw capability (multimodal, gameplay) that I think is still quite lacking.
1,802
2,314
750
29,752
6,273,180
Dan Harper retweeted
When Claude comes to me with a wall of text like “I smoke-verified the config-guarded ‘one authority per tibble‘ materialization core (clean), but the metadata-bearing patches (no-op) are spec-shaped—and that’s a call that’s genuinely yours.”
98
382
67
5,693
661,572
Dan Harper retweeted
I'm 33 and I think Claude Code is melting my brain. For 6 months straight I've had 5-6 terminals open at once, waiting on responses just to smash "enter" 90% of the time. That's the whole job now. And it's doing something to me. A few friends and I keep circling back to the same thing in conversations: none of us feel as sharp as we used to. Maybe it's just us. But I keep wondering how many other people in their 30s feel it too. (And yeah: this is a me problem, how I lean on the tool, not the tool itself. Doesn't make the effect any less real.)
Readers added context they thought people might want to know
This is directly plagiarised from a viral post from @astnkennedy, with the only change being the age. x.com/astnkennedy/st…
2,138
581
459
12,505
1,846,198
*one* Extra High Sol prompt, 4 minutes, and I've hit the 5 hour quota 😳
114
ChatGPT just pulled a Microsoft… Codex is now ChatGPT(?) and ChatGPT is now ChatGPT Classic.
1
393
Anthropic have the opportunity to do the funniest thing: block Coinbase’s Claude access.
This is an email I sent earlier today to all employees at Coinbase: Team, Today I’ve made the difficult decision to reduce the size of Coinbase by ~14%. I want to walk you through why we're doing this now, what it means for those affected, and how this positions us for the future. Why now Two forces are converging at the same time. We need to be front footed to respond to both. First, the market. Coinbase is well-capitalized, has diversified revenue streams, and is well-positioned to weather any storm. Crypto is also on the verge of the next wave of adoption, with stablecoins, prediction markets, tokenization, and more taking off. However, our business is still volatile from quarter to quarter. While we've managed through that cyclicality many times before and come out stronger on the other side, we’re currently in a down market and need to adjust our cost structure now so that we emerge from this period leaner, faster, and more efficient for our next phase of growth. Second, AI is changing how we work. Over the past year, I’ve watched engineers use AI to ship in days what used to take a team weeks. Non-technical teams are now shipping production code and many of our workflows are being automated. The pace of what's possible with a small, focused team has changed dramatically, and it's accelerating every day. All of this has led us to an inflection point, not just for Coinbase, but for every company. The biggest risk now is not taking action. We are adjusting early and deliberately to rebuild Coinbase to be lean, fast, and AI-native. We need to return to the speed and focus of our startup founding, with AI at our core. What this means To get there, we are not just reducing headcount and cutting costs, we’re fundamentally changing how we operate: rebuilding Coinbase as an intelligence, with humans around the edge aligning it. What does this mean in practice? - Fewer layers, faster decisions: We are flattening our org structure to 5 layers max below CEO/COO. Layers slow things down and create coordination tax. The future is small, high context teams that can move quickly. Leaders will own much more, with as many as 15+ direct reports. Fewer layers also means a leaner cost structure that is built to perform through all market cycles. - No pure managers: Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams. - AI-native pods: We’ll be concentrating around AI-native talent who can manage fleets of agents to drive outsized impact. We’ll also be experimenting with reduced pod sizes, including “one person teams” with engineers, designers, and product managers all in one role. In short: AI is bringing a profound shift in how companies operate, and we’re reshaping Coinbase to lead in this new era. This is a new way of working, and we need to leverage AI across every facet of our jobs. To those who are affected I know there are real people behind these decisions — talented colleagues who have poured themselves into this company and our mission. To those of you who will be leaving: thank you. You’ve helped build Coinbase into what it is today, and I am sincerely grateful for everything you've done. All impacted team members will receive an email to their personal account in the next hour with more information, and an invitation to meet with an HRBP and a senior leader in your organization. Coinbase system access has been removed today. I know this feels sudden and harsh, but it is the only responsible choice given our duty to protect customer information. To those affected, we will be providing a comprehensive package to support you through this transition. US employees will receive a minimum of 16 weeks base pay (plus 2 weeks per year worked), their next equity vest, and 6 months of COBRA. Employees on a work visa will get extra transition support. Those outside of the US will receive similar support, based on local factors and subject to any consultation requirements. Coinbase prides itself on talent density. Our employees are among the most talented people in the world, and I have no doubt that your skills and experience will be highly sought after as you pursue your next chapters. How we move forward To the team that is staying, I know this is a difficult day. We’re saying goodbye to colleagues and friends you've been in the trenches with. But here’s what I want you to know as we move forward together: Over the past 13 years, we have weathered four crypto winters, gone public, and built the most trusted platform in our industry. We’ve made it this far by making hard decisions and by always staying focused on our mission. This time will be no different – nothing has changed about the long term outlook of our company or industry. And most importantly, our mission has never been more important for the world. Increasing economic freedom requires a new financial system, and we’re building it. The Coinbase that emerges from this will be more capable than ever to achieve our mission. Brian
1
140
Dan Harper retweeted
slowly starting to use plan mode a LOT less nowadays i realised whenever i use plan mode, it generates a gigantic plan and then i dont read it and hit build out of laziness having a meaningful conversation with the AI agent to discuss implementation feels a lot easier 🤔
103
22
28
773
799,870
Dan Harper retweeted
asking Claude to create a prompt for my other Claude
135
982
65
28,072
549,921
Dan Harper retweeted
Here’s what’s gonna happen: - you replace your code review with feedback loops (sentry, datadog, support tickets, etc) - you stop reading the code - software factory fixes everything - one day something breaks at 3am, agent can’t fix it - nobody’s read the code in 3 months - you have 3 weeks of downtime trying to re-onboard and fix it - you lose significant % of your contracts and users - your company is now dead
Replying to @gregpr07
this may surprise you that thus is coming from me but I think we’re in for a 1-3 year period where stuff might break at 3am and if you’re relying on loops to fix it and nobody understands what’s under the hood, you’re looking at an existential threat to your company
248
540
111
6,720
630,934
Dan Harper retweeted
"Shipping a button" (vid by @KaiLentit). Might be the funniest thing I've seen in years
70
317
82
2,828
311,222
Dan Harper retweeted
when the whole team is on claude code
200
1,009
147
13,316
1,014,603
Four types of people at every company now yes, people get 10x better when the go from bottom right to top right but also, people get 10x worse when they go from bottom left to top left
156
437
172
4,470
674,047
actual footage of Anthropic FDEs arriving to automate your back office
JUST IN: Anthropic engineers have spent six months at Goldman building autonomous systems for time-intensive, high-volume back-office work
18
123
7
3,551
202,746
Kind of mind-blowing experience with Claude Code today. I wanted to get an old Debian 4.0 VM (don't ask) running on my Mac. It wouldn't immediately boot in VirtualBox, so Claude Code walked me through some debugging steps… Then I realised it'd be much better if I just put it in the driver's seat… I asked one instance to get it running, and another in parallel to just extract files from the image. Here's Claude, in its own words:
1
104
Two instances, two completely different strategies, both working autonomously. One reverse-engineered the boot chain and binary-patched a disk image. The other wrote a filesystem parser from scratch to bypass the OS entirely. The VM is from 2007. The AI debugging it is from 2026. What a time.
1
30
Back to me: wtaf. No idea if there was a better way – it's a "solved" problem, but these 2 just went and got it working while I had lunch. One patched the image to get it working. The other wrote a reader to extract the files from it.
23