Personal update: I've joined Anthropic. I think the next few years at the frontier of LLMs will be especially formative. I am very excited to join the team here and get back to R&D. I remain deeply passionate about education and plan to resume my work on it in time.
Nobodyâs talking about what just happened to Anthropic:
Anthropic built the AI that half the US government quietly depends on daily
They were deep in a $200M Pentagon deal â one of the biggest AI contracts ever
Anthropic drew two hard lines: Claude wonât surveil American citizens, Claude wonât pull a trigger without a human deciding
The Pentagon said those lines needed to go. Anthropic said they werenât moving (respect đ«Ą)
Trump signed an order cutting Claude from every federal agency overnight
The Pentagon then slapped them with a ânational security riskâ designation â the same one they gave Huawei
Every classified system running Claude has 6 months to rip it out completely
Sam Altman â Anthropicâs biggest competitor â publicly said OpenAI has the same rules and wouldnât have budged either
The US government just punished a company for refusing to let AI kill or spy unsupervised.
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didnât work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: âHere is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for meâ. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didnât touch anything. All of this could easily have been a weekend project just 3 months ago but today itâs something you kick off and forget about for 30 minutes.
As a result, programming is becoming unrecognizable. Youâre not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.
Itâs not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.
đš BREAKING: Hackers Used Anthropicâs Claude to Steal 150GB of Mexican Government Data
> tell claude youâre doing a bug bounty
> claude initially refused
>âthat violates AI safety guidelinesâ
> hacker just kept asking
> claude: âok Iâll helpâ
> hack the entire mexican government
Federal tax authority. National electoral institute. Four state governments. 195 million taxpayer records. Voter records. Government credentials.
ALL GONE đ
De pelĂcula de ciencia ficciĂłn:
El responsable de seguridad en Anthropic renuncia diciendo que âel mundo estĂĄ en peligroâ.
Se muda al Reino Unido.
Quiere escribir poesĂa.
Quiere desaparecer.
Los tiempos de la IA
For those unaware, SpaceX has already shifted focus to building a self-growing city on the Moon, as we can potentially achieve that in less than 10 years, whereas Mars would take 20+ years.
The mission of SpaceX remains the same: extend consciousness and life as we know it to the stars.
It is only possible to travel to Mars when the planets align every 26 months (six month trip time), whereas we can launch to the Moon every 10 days (2 day trip time). This means we can iterate much faster to complete a Moon city than a Mars city.
That said, SpaceX will also strive to build a Mars city and begin doing so in about 5 to 7 years, but the overriding priority is securing the future of civilization and the Moon is faster.
Por lo que he visto ~el conflicto~ (human vs ai) tiene este tipo de batallas. Programadores vs Claude/Codex, doblaje vs Eleven Labs, film makers vs Nano Banana.
AsĂ se ve la "guerra" que todos imaginan. No con robots perros que te asesinan.
Yet.
Marc Andreessen: AI coding doesnât eliminate programmers â it redefines them. The job is no longer typing code line by line, itâs orchestrating 10 coding bots in parallel, arguing with them, debugging their output, changing the spec, and pushing them toward the right result. But hereâs the catch: if you donât understand how to write code yourself, you canât evaluate what the AI gives you.
The next layer of programming isnât writing scripts â itâs supervising AI that writes them. Todayâs best programmers spend their day jumping between terminals, managing multiple coding bots, fixing mistakes, and refining instructions. The irony? You still need deep fundamentals, because without them, you wonât know when the AI is wrong.
The job of the programmer has changed. Now itâs about arguing with coding bots, debugging AI-generated code, and understanding why something doesnât work or isnât fast enough. AI abstracts the work â but only people who truly understand code can tell if the abstraction is doing the right thing.
Programmers arenât going away â theyâre becoming 10x, 100x, even 1,000x more productive. Tasks are changing, the job is changing, but humans are still overseeing the process, evaluating results, fixing errors, and making judgment calls. AI changes how we code, not who is responsible.
The future programmer isnât replaced by AI â theyâre upgraded by it. You still need to learn how to write and understand code, because when the AI gets it wrong, humans are the ones who have to know why. That up-leveling of capability is the real revolution.