Andrew Kouri

@ThomasAlxDmy It seems like autopilot on HW3 is totally unmaintained. It has had the same phantom braking and horrible jerkiness of acceleration after the last code change they did a couple years ago and has never gotten better. Kinda sad. It was way better when I first bought the car.

@ThomasAlxDmy I have HW3 and autopilot (non-FSD) is straight up unusable. I'd actually use the word dangerous. To me it seems like they have two parallel codebases running, rather than a single unified codebase with feature flags for FSD/autopilot

Unpopular opinion: Stop whining about your old car and upgrade to a much better version - it will change your life

Claude Status Page vs Whole Foods Three Pepper Blend Who wore it better?

@recap_david Renovate

I turned a Zillow listing into a cinematic property renovation video for $15 (no camera, no drone, no film crew) Just listing photos + Calico AI. Most agents are paying $100-$500 per property for videos at this quality. Offer this to realtors in your area and print money. Here's how the workflow breaks down: → Grab listing photos from any property (Zillow, Redfin, take your pick) → Lock in one consistent renovation style across the whole house → Generate photorealistic after-renovation images → Animate the transformation in every room → Build a cinematic closing shot with the realtor's contact info → Drop in a custom music track → Stitch it all together The result: a scroll-stopping property video that gets buyers dialing — built entirely from photos that were already on the listing. No videographer. No staging budget. No waiting around for golden hour. Comment "RENOVATE" and I'll send over the full workflow + every prompt + a step-by-step walkthrough video (gotta be following so the DM goes through!).

new concept: reverse retirement i do what i want until i'm 60 and then get a shitty desk job for the rest of my life

@sama lol

Tonight, we reached an agreement with the Department of War to deploy our models in their classified network. In all of our interactions, the DoW displayed a deep respect for safety and a desire to partner to achieve the best possible outcome. AI safety and wide distribution of benefits are the core of our mission. Two of our most important safety principles are prohibitions on domestic mass surveillance and human responsibility for the use of force, including for autonomous weapon systems. The DoW agrees with these principles, reflects them in law and policy, and we put them into our agreement. We also will build technical safeguards to ensure our models behave as they should, which the DoW also wanted. We will deploy FDEs to help with our models and to ensure their safety, we will deploy on cloud networks only. We are asking the DoW to offer these same terms to all AI companies, which in our opinion we think everyone should be willing to accept. We have expressed our strong desire to see things de-escalate away from legal and governmental actions and towards reasonable agreements. We remain committed to serve all of humanity as best we can. The world is a complicated, messy, and sometimes dangerous place.

China is moving rapidly to a solar/electric future with very little need for oil or gas

@SecWar Disgusting. This is not the America I grew up in.

This week, Anthropic delivered a master class in arrogance and betrayal as well as a textbook case of how not to do business with the United States Government or the Pentagon. Our position has never wavered and will never waver: the Department of War must have full, unrestricted access to Anthropic’s models for every LAWFUL purpose in defense of the Republic. Instead, @AnthropicAI and its CEO @DarioAmodei, have chosen duplicity. Cloaked in the sanctimonious rhetoric of “effective altruism,” they have attempted to strong-arm the United States military into submission - a cowardly act of corporate virtue-signaling that places Silicon Valley ideology above American lives. The Terms of Service of Anthropic’s defective altruism will never outweigh the safety, the readiness, or the lives of American troops on the battlefield. Their true objective is unmistakable: to seize veto power over the operational decisions of the United States military. That is unacceptable. As President Trump stated on Truth Social, the Commander-in-Chief and the American people alone will determine the destiny of our armed forces, not unelected tech executives. Anthropic’s stance is fundamentally incompatible with American principles. Their relationship with the United States Armed Forces and the Federal Government has therefore been permanently altered. In conjunction with the President's directive for the Federal Government to cease all use of Anthropic's technology, I am directing the Department of War to designate Anthropic a Supply-Chain Risk to National Security. Effective immediately, no contractor, supplier, or partner that does business with the United States military may conduct any commercial activity with Anthropic. Anthropic will continue to provide the Department of War its services for a period of no more than six months to allow for a seamless transition to a better and more patriotic service. America’s warfighters will never be held hostage by the ideological whims of Big Tech. This decision is final.

Since @Nextdoor keeps blatantly ignoring the CAN-SPAM act, I made a little cheat sheet to help anyone else who can’t unsubscribe from their relentless emailing. Enjoy! Cc @FTC

@elonmusk Donate it all to worthy causes before you die and then the government won’t be able to take it. Your impact on bringing human life to mars could be more attainable when it doesn’t need to be done at a profit. You’ve earned the right to play life on EZ mode

I will probably end up paying over $500B in taxes, inclusive of death

The neuroscience here is more radical than people realize. What you’re watching is a hormonal phase transition. Within minutes of skin-to-skin contact with a newborn, a father’s endocrine system starts a cascade that rewires his brain for the next 20 years. Testosterone drops 34% on average. Gettler’s 2011 landmark study at Notre Dame tracked 624 men and found that the ones who spent 3+ hours per day in direct childcare had the steepest declines. This matters because testosterone and parental sensitivity are inversely correlated. Lower T predicts more responsiveness to infant cues, more physical touch, more synchrony with the child’s emotional states. Meanwhile, oxytocin surges 33% above non-father baselines. Prolactin spikes. Estradiol rises. These are the same hormones that activate in mothers during pregnancy and breastfeeding. The entire “maternal bonding” cocktail fires in fathers through a different delivery mechanism: proximity and touch. Here’s where it gets wild. Dr. Pilyoung Kim at the University of Denver scanned fathers’ brains at 2-4 weeks postpartum and again at 12-16 weeks. The regions linked to attachment, empathy, and threat detection showed measurable increases in gray and white matter. The brain physically bulked up in areas responsible for protection and caregiving. And in mice studies, neurogenesis (new neuron formation) occurred in father brains within days of their pups being born. But only in fathers who stayed in the nest. The ones removed on day one showed zero new neuron growth. Physical contact was the switch. So the claim about brains being “literally rewired for protection” actually undersells it. The father’s brain grows new tissue. It shifts its entire hormonal architecture from mating optimization to caregiving optimization. The reward circuitry that previously activated for sexual stimuli redirects toward child faces and infant cries. The biological mechanism for fatherhood is one of the most aggressive neuroplastic events in the adult male lifespan. And it’s entirely dose-dependent: more contact, more holding, more time in proximity = stronger the neural and hormonal shift. That first hold is a pharmacological event.

41.3% of young males with cannabis-induced psychosis develop schizophrenia within 3 years.

Software engineers are the happiest people on Earth now. They pay $100/month for Claude Code to do the work. Their employer pays them $10,000/month for the results. $9,900 profit for sipping coffee and talking to AI. What a time to be alive.

My favorite thing so far in 2026: Wake up and put a 10lb tiny human on my chest and we both just lay and breathe for an hour. Nothing like it. But yeah ClawMolt or whatever is cool too

sf escape room called The Permanent Underclass and it’s just a room with a laptop and claude code installed

How it feels when AI can't solve your problem and you switch to documentation🤣🤣🤣

Babies are easy because when they are upset it is one of three easily verifiable things (hungry/tired/poopy). Toddlers are hard because when they are upset it is because you disrupted some perceived esoteric order to the cosmos that is nearly inscrutable. Like “you can’t put the green crayon next to the purple crayon because banana goblins”

engineers watching the BD team use claude code

@karpathy @0xabi96 tenor.com/R4Y9.gif Everybody has superpowers now.

@0xabi96 It feels like I’m cheating. Which is a very weird feeling to have. It takes a while to unpack. It’s because some code that used to be a point of pride and high IQ and knowledge is suddenly free and instant and it’s very disorienting.

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.