Loading video...

Video Failed to Load

Go Home

Marc Andreessen (the guy who called it when “software ate the world”) just pointed out what AI is doing to coding next. “Everyone assumes AI coding means fewer hours… or leaving the profession. But almost everyone I know is working more hours.” “There’s a new term in the Valley:...

138,697 views • 1 month ago •via X (Twitter)

33 Comments

Just a guy's profile picture
Just a guy1 month ago

Marc conflates more code with greater value, much of this extra output is lower quality and riddled with bugs. Lots of literature in this. Interesting that Marc doesn't mention this.

Howard the Duck's profile picture
Howard the Duck1 month ago

Precisely. I have been programming for 60 years, and the last 3 months with Claude Code have been my most productive yet, and half the time was getting Claude up to speed with how I wanted to do things.

aryaman kalia's profile picture
aryaman kalia1 month ago

Let me tell you coders are contol freaks . I have seen developers discard a entire pr because of a variable name is wrong "according to them". So you write code with Ai . And then bang your head because you don't understand what it fucking wrote .... The video is BULLSHIT ...

naan_sequitur's profile picture
naan_sequitur1 month ago

that nose sniff he uses to emphasize his words is such a distracting tic

Berty Noman's profile picture
Berty Noman1 month ago

Such bullshit lol.

IdRatherBePlayingPinball's profile picture
IdRatherBePlayingPinball1 month ago

This guys friend made a “digital jukebox of his dreams” with AI? Has this motherfucker ever heard of a Spotify playlist?

Buttlehun's profile picture
Buttlehun1 month ago

50m a year lol ok prove it

Sanjay Raj Sharma's profile picture
Sanjay Raj Sharma1 month ago

50 million 😂

Tech Signal's profile picture
Tech Signal1 month ago

This is very true. But it also means projects will get finished way faster and with much less human brain function. Meaning you will need less and less people.

Sonny Lowry's profile picture
Sonny Lowry1 month ago

@samrexford Thought of you when I saw this. You shouldn't be sleeping as my boy Andreessen says.

Name Here's profile picture
Name Here1 month ago

‘AI PSYCHOSIS’

Andrej Szontagh's profile picture
Andrej Szontagh1 month ago

Well, but that is very likely just a temporary situation. Because there is in fact not an infinite demand for software. Nothing is infinite, and surely not software demand. Software profits will go down, and a lot of those extra cases AI can do now will still be pointless to make

LexDiamondHQ's profile picture
LexDiamondHQ1 month ago

The inhales are insane

Crypto Nikko's profile picture
Crypto Nikko1 month ago

This is all bs.

Mark Nissley's profile picture
Mark Nissley1 month ago

It started in coding but the AI vampire is everywhere now. You can go so deep on *anything*, that just about everything can become a project. Coding an app for my kids, the family vacation, stock option trading, retirement planning, a fitness regime,...

John Jacob Jingle's profile picture
John Jacob Jingle1 month ago

This guy sucks now. What a fall from grace.

Agentic Bull's profile picture
Agentic Bull1 month ago

This is the part of the AI productivity story people miss: When the cost of capability collapses, ambition doesn’t stay fixed. Backlogs become possible. Small teams attempt big projects. Individuals build things that once required companies. The Agentic Economy won’t just do the same work faster. It expands the amount of work worth doing. 🐂

Dancyg's profile picture
Dancyg1 month ago

“More code per hour” this egghead doesn't know shit.

pc0's profile picture
pc01 month ago

Just cause you can build it does t mean you should. More top of strategy funnel wisdom required.

AI Evolution's profile picture
AI Evolution1 month ago

Interested in AI? Follow @AiEvolutio58513 and never fall behind. I track ChatGPT, Claude, and every tool quietly changing how we work and create, then hand you the tested signals.

Mladen Mihajlovic's profile picture
Mladen Mihajlovic1 month ago

$50 mil a year! Haahhahahah I wonder if these guys have a good laugh off camera about the crap they say 😂🤣

John Smith's profile picture
John Smith1 month ago

Much of this is "noise". Whoever figures out how to shut up "chatty kathy", and focus on valuable results will win the coding war. Guessing Elon has already figured that out. (Grok and Community Notes for example)

USA's profile picture
USA1 month ago

“All Coding Is Flawed, With Computing Products That Drain Energy, Instead Of Producing Power?”

gasmat's profile picture
gasmat1 month ago

"The cost of going to sleep is to high" Shut the fuck up...

The Mad Stoic's profile picture
The Mad Stoic1 month ago

After men who dug dirt with their hands invented shovels, they didn't spend less time digging.

Responsibility Begins Here's profile picture
Responsibility Begins Here1 month ago

AI can write code faster. Fine. But the first run is where reality gets a vote. You can model the process, write the planning, build the instructions and let AI optimize every line. Then you put the first unit through the actual machine and discover what the drawing, model or code did not know. That is why first article work matters. You run it. You redline it. You measure it. You watch the material, tooling, sequence, vibration, temperature, variation and throughput. Then the people who actually understand the process decide what is preferred, what is acceptable and what is rejectable. And somebody still has to own that decision. AI can recommend the disposition. It cannot sign its name to it. Now feed that back into AI. Revise the code. Revise the planning. Incorporate the redlines. Run it again. That is the loop. AI does not eliminate engineering or experience. It gives both a much faster tool. The engineer understands why the process should work. The person living with that process knows when it actually does. Put those two together with AI and now you have something powerful: human experience teaching the machine, the machine accelerating the correction, and every run making the next one better. The future is not man versus machine. It is the experienced human standing beside the machine saying: “That passed the specification. Now let me show you how to make it right.🙏🧎🇺🇸

Tuck Fuck's profile picture
Tuck Fuck1 month ago

Wow life sounds great, Marc

Aleksandar Janca's profile picture
Aleksandar Janca1 month ago

hours didn't move, the job did. i write less and review more. read 200 customer reviews in 20 minutes last month because the model drafted and i just edited. felt lighter, took the same afternoon. editing is harder than writing and nobody warned anyone about that part. has your week gone the same way or are you still writing most of it

Andrew Allen 💹🧲's profile picture
Andrew Allen 💹🧲1 month ago

I think so too🤷🏽 but apparently that’s controversial to say😂 the truth always is

Gertywood's profile picture
Gertywood1 month ago

Yeeeep. My work hours went from 6 hours is like 11 hours. Making AI movies alllll day long. It’s wild.

Ondřej Mlček's profile picture
Ondřej Mlček1 month ago

Add some sleep checks to cursor ))

O-'s profile picture
O-1 month ago

???

Brian Mosley's profile picture
Brian Mosley1 month ago

No, the reason Devs are working night and day is token anxiety... Not knowing when @thsottiaux might hit the reset button lol

Related Videos

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.

Ian Miles

913,594 views • 8 months ago

Marc Andreessen says the best engineers alive stopped sleeping on purpose, and every one of them calls it the happiest they’ve ever been. Andreessen: “You’re up all night doing AI coding because you’re getting so much done that you can’t turn off. The opportunity cost of going to sleep is too high.” The body has one price it never negotiates. An hour of this just cleared it. They call them AI vampires now. Twenty agents working the night shift, and one human who refuses to be the bottleneck in his own life. Andreessen: “They’re sleep deprived, they’ve got bags under their eyes, they’re clearly not taking care of themselves. And they’re absolutely ecstatic.” Burnout is exhaustion in the absence of meaning. This is the reverse. Exhaustion from an oversupply. It was supposed to make us obsolete. It made us insatiable. We have only ever met desire in a cage. Uncaged, we call it sickness. Wanting more than you could reach was a wound with no treatment, so we made a virtue of not wanting. Moderation. Contentment. Being realistic. Knowing your limits. Handed down as wisdom. All of it anesthesia for a species that could not afford its own ideas. Underneath the vampires sits a quieter story that does far more damage. A friend on Wall Street. MIT computer science degree, thirty five years ago. Then the market bid higher for his hours, and he put it down for three decades. Andreessen: “He’s picked up coding with AI. He’s completely re-automated his entire house.” Nothing was resurrected. Nothing had ever died. Andreessen: “…in his spare time has generated 500,000 lines of code, just by working with AI.” He never lacked the vision. He lacked the hours. Three decades of wanting with nowhere to put it. Desire doesn’t die when you starve it. It goes quiet, and you start describing it in the past tense. Andreessen: “The coders that are using AI, the estimate is right now that they’re 20 times more productive than they were before they started using AI.” Not twenty percent. Twenty times. He draws the pessimistic case from it himself. Andreessen: “If there’s only a limited amount of software that people want in the world, then yeah, you’re going to get mass unemployment.” One clause in that sentence holds up the entire automation debate. A limited amount that people want. Every number we have on human demand was taken inside a rationing regime. We measured the ideas that could clear a payroll. Everything beneath that line never existed long enough to be counted. The house that works the way you pictured it. The fix nobody else needs. The idea too small to fund and too personal to sell. We spent a century measuring the supply curve and filed the result under human nature. Nobody alive has ever seen what a person wants. Only what they could afford to want. You were never a person with limits. You were a person with prices. Scarcity was never only a constraint. It was an alibi. It let everyone believe the life they never lived was taken from them. I would have, but. There is no but anymore. The vampires aren’t up all night because the machine demands it. They’re up because the thing they always meant to make finally stopped being impossible. You have one too. You’ve just been describing it in the past tense. That was never a verdict on you. It was a price. The price went to zero.

Dustin

21,283 views • 2 months ago

Marc Andreessen explains why AI coding won't replace programmers, but fundamentally change what they do. He argues that AI coding is just the latest abstraction layer, and the job of a programmer has always evolved with each one. Andreessen's key reframe of what's actually happening: "AI coding actually abstracts away the process of actually writing the scripting code... This is the next layer of the task redefinition under the job of programmer." He's clear that the best programmers aren't being replaced. They're already adapting, even if their day-to-day looks radically different now. Their job has shifted from writing code line by line to managing dozens of AI agents working in parallel. "The world's best programmers today will tell you, 'My job is I'm sitting there and I'm orchestrating 10 code bots running in parallel.' Their day job now is kind of arguing with the AI bots to try to get them to write the right code." But Marc Andreessen 🇺🇸 is adamant this doesn't make foundational knowledge obsolete — it makes it more important. "You need to still fully understand and learn how to write and understand code, because if it doesn't work or it's not doing what you expect, you need to be able to understand the results of what the AI is giving you." He draws a direct parallel: Just as someone writing scripting languages still needs to understand how a microprocessor works, someone orchestrating AI bots needs to understand the code those bots produce. "It's this upleveling of capability where you actually want the depth to go down and understand what the thing is actually doing, even if you're not spending your day doing that by hand." The result, in his view, is transformative: "Now programmers are going to be 10 times or 100 times or a thousand times more productive. And that is overwhelmingly a good thing." The pattern: New abstraction layer emerges → tasks change → the job gets redefined upward → productivity explodes It raises a question every programmer should be sitting with... Are you building the depth to evaluate what AI gives you, or just accepting the output?

Big Brain AI

45,371 views • 7 months ago