Загрузка видео...

Не удалось загрузить видео

На главную

The creator of Ruby on Rails just said programmers may be worse at AI coding than people who cannot code. Lex Fridman asked David Heinemeier Hansson directly. His answer: 100%. Because once the AI handles the implementation, knowing how to write a loop is no longer the rare skill....

143,315 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 41

Фото профиля Adrian Novischi
Adrian Novischi2 месяцев назад

LOL. That's assumes that AI agents perfectly implement what you tell them, and if you just give them a general ask they will precisely fulfill your wishes and the language we speak is perfectly clear with no ambiguities and all words have a single clear sense.

Фото профиля Achim Friedland 🏴󠁧󠁢󠁥󠁮󠁧󠁿
Achim Friedland 🏴󠁧󠁢󠁥󠁮󠁧󠁿2 месяцев назад

Yes… that‘s why ruby-on-rails was always nice but slow as hell! It is NOT enough to specify what the user wants, you also have to specify the technical details sometimes down to registers and database indices.

Фото профиля Ihtesham Ali
Ihtesham Ali2 месяцев назад

Very true and accurate

Фото профиля Andrew Apell | Software Generalist
Andrew Apell | Software Generalist2 месяцев назад

Skill issue... Next he will blame a hammer for not knowing how to drive a nail into wood.

Фото профиля Ihtesham Ali
Ihtesham Ali2 месяцев назад

🤣 you are talking about a legend here

Фото профиля Andrew Apell | Software Generalist
Andrew Apell | Software Generalist2 месяцев назад

😂🤣😂 I know but since 2016 I have been ignoring medals one might have and looking at what is right before me. You would be surprised how many times that has helped me.

Фото профиля Ihtesham Ali
Ihtesham Ali2 месяцев назад

yes, i can see where you are pointing at. Got it

Фото профиля scLLptr
scLLptr2 месяцев назад

I call this hyper-vibe ai evangelism.

Фото профиля Ihtesham Ali
Ihtesham Ali2 месяцев назад

Are you aware of DHH?

Фото профиля scLLptr
scLLptr2 месяцев назад

A am aware of ridiculousity of his claim. AI is 5 years from replacing whole SWE. It's too early now. This short phase is the phase of AI boosted fake confidence.

Фото профиля sajid 💫
sajid 💫2 месяцев назад

there are good product guys who are also programmers.

Фото профиля Lucidos
Lucidos2 месяцев назад

I agree for the coder if they're a jira factory worker. But a good software developer has always been the one with an architectural eye and that is still needed. Along with knowing what product to build and what makes it great. Architecture has no value on its own. It's what lets you evolve a great product.

Фото профиля Durbek
Durbek2 месяцев назад

This is so confusing. You are saying that programmers are worse at AI because they can't do the product design? But even before AI, programmers were not doing product design. You are mixing up product design and programming. And adding AI here out of nowhere like wth.

Фото профиля ArthurMxn 🇲🇽🇺🇲
ArthurMxn 🇲🇽🇺🇲2 месяцев назад

Totally agree! 💯 Working with my nephew, a programmer, on construction takeoff software. I'm the estimator, and I've used other software. He's full of technical jargon about all his implementation ideas – some great, some not so much. Ultimately, as the user, I know what needs to be built. 👷‍♂️💻

Фото профиля Nick Stewart
Nick Stewart2 месяцев назад

This starts to break down when you are unable to describe the problem since you don’t have the pre-requisite knowledge needed

Фото профиля José Manuel
José Manuel2 месяцев назад

This is the most retard take that I've seen.

Фото профиля SoftwareGuy
SoftwareGuy2 месяцев назад

I get his point, my take is micromanagement. But I think I'd like my AI surgery to be overseen by a "surgeon" and not a "prompt surgeon".

Фото профиля 0xful 🇪🇺
0xful 🇪🇺2 месяцев назад

He forgot that the coding agents were trained on human written code... which is average...

Фото профиля FreeRoamer
FreeRoamer2 месяцев назад

yes and no. For an excellent result you need to know what is going on behind the seams. Also, once the product reaches the masses you NEED to understand the system and tech stack, one mistake and your db is gone, you get hacked, get denials of services, nasty bugs etc.

Фото профиля Philip
Philip2 месяцев назад

People with good taste will create the best products.

Фото профиля Nick Losciuto
Nick Losciuto2 месяцев назад

Well, that guy makes an awesome guest

Фото профиля P@ulLuo
P@ulLuo2 месяцев назад

You do realize ai generated code gets it wrong too sometimes? Somebody has to review generated code. Lol

Фото профиля luan au
luan au2 месяцев назад

Any evidence so far?

Фото профиля dreadnaught
dreadnaught2 месяцев назад

hahahahahaha we've finally made it! so the nerds they employ are totally smart enough to use it, just not the other billion nerds out there. it's almost as stupid as the "opus 5 isn't bad you just have to purge everything from your environment for it to be good" stuff from the other month lol

Фото профиля David Joffe ⌨🖌🎨
David Joffe ⌨🖌🎨2 месяцев назад

Yes and no. As an experienced developer I know software is complex and AIs also may add bugs or sometimes subtly incorrect behaviors that take valuable time to check. Just assuming some code works is a recipe for trouble. Software is a lot more complex than just "writing loops".

Фото профиля Crypto Cabrón
Crypto Cabrón2 месяцев назад

Product owners are kings

Фото профиля Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBack2 месяцев назад

@ihteshamali honestly, it's wild to think about. feels like we're all just learning how to speak the AI's language now

Фото профиля wensei🔥
wensei🔥2 месяцев назад

Meu vizinho, dev senior, obeso, mora com a mãe em Sapopemba, 45 anos, disse que ele é insubstituível e que em breve vai ficar rico arrumando bugs em códigos feito por vibe coders.

Фото профиля Vishnu Chilamakuru
Vishnu Chilamakuru2 месяцев назад

Absolutely. Now writing code is not a moat. Understanding domain knowledge, knowing what should be the expected behaviour, what are all flows needs particularl change, all the domain level context became much important.

Фото профиля Pockets Full ⭕f NFT's
Pockets Full ⭕f NFT's2 месяцев назад

Final someone not afraid to tell the truth

Фото профиля Nav Toor
Nav Toor2 месяцев назад

Code is becoming the easy part

Фото профиля Alfred
Alfred2 месяцев назад

I am a Solution Architect and I agree with DHH

Фото профиля Ihtesham Ali
Ihtesham Ali2 месяцев назад

Many would agree.

Фото профиля Simon Smith
Simon Smith2 месяцев назад

It’s not like product managers with excellent product understanding have made unreasonable requests for decades already. The problem with today’s coding agents is that they won’t say no, and will move mountains of code to satisfy any architectural disaster.

Фото профиля Brian Gastón
Brian Gastón2 месяцев назад

This tracks hard. I don’t win because I can code better than a senior. I win because I know the bar, the rush, the boring problems that actually matter. AI can implement. I decide what deserves to exist.

Фото профиля KnightHawk
KnightHawk2 месяцев назад

Great for people who understand intuitive UX and product but also used to code.

Фото профиля Zack
Zack2 месяцев назад

A lot of non tech founders are realizing this and jumping in the pool themselves

Фото профиля ppalme Cont.Learning
ppalme Cont.Learning2 месяцев назад

What advantage now belongs to the person ….

Фото профиля Religion is poison
Religion is poison2 месяцев назад

Twisting his words, he said "there are problems" (not all problems), which any good programmer knows already.

Фото профиля 0x21
0x212 месяцев назад

Absolutely nailed it

Фото профиля Muhammad Suleman
Muhammad Suleman2 месяцев назад

i see his point first you make code work like an average joe but after that you also need to challenge it....LLM will usually contradict itself in longer discussion ...you give it few more lines of new context and it may totally abandon previous strategy

Похожие видео

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 просмотров • 8 месяцев назад

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

MIKE

39,041 просмотров • 4 месяцев назад

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 Cheong

914,018 просмотров • 9 месяцев назад

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

195,059 просмотров • 6 месяцев назад

Sam Altman told the world exactly what skills will matter when AI takes over 30 to 40 percent of the global economy. He was asked what his own kids should do to survive it. His answer was surprisingly human. He said the single most valuable thing anyone can build right now is the meta-skill of learning how to learn. Not a degree or a certification but the raw ability to adapt when everything around you changes. He also said learning to understand what other people actually want and building useful things for them will be more valuable than almost any technical knowledge. That skill has never been automated and is not close to being automated. He said human creativity and the desire to express it are, in his words, limitless. Every major technological revolution increased the demand for creative, curious, and socially intelligent people, not decreased it. The Industrial Revolution is the clearest parallel. Machines replaced physical labor and people were terrified. The next generation took those machines and built industries, art forms, and institutions nobody had conceived of before. The people who thrived were not the ones who competed with the machines. They were the ones who learned to direct them toward something new. That dynamic is already playing out right now with AI. The practical implication is this, depth in a single rigid skill is becoming less valuable. The ability to move across domains, pick up new tools quickly, and apply judgment in ambiguous situations is becoming more valuable. Altman also pointed to something most career advice ignores entirely, learning how to interact with the world, build relationships, and earn trust from other people. Those are things AI can simulate but cannot replace. The honest opportunity in this moment is not to outrun AI. It is to focus on the things that make you irreducibly human. Curiosity, judgment, empathy and the ability to ask the right question before anyone knows what the right question is. The people who will matter most in an AI-driven economy are not necessarily the ones who understand the technology deepest. They are the ones who can figure out what the technology should actually be used for. Altman has spent his career betting on human potential in the face of technological disruption. Based on every historical precedent, that is still the right bet to make.

StockMarket.News

377,183 просмотров • 7 месяцев назад

Dario Amodei just announced the end of software engineering as a profession. The timeline is 6 to 12 months. Amodei: “I have engineers within Anthropic who say, I don’t write any code anymore. I just let the model write the code. I edit it.” Not a prediction. Current reality inside the frontier lab. The engineers who built the most advanced AI in the world have stopped writing code. They supervise. They edit. They manage architecture. The craft they spent careers mastering has been handed to the system they built. Amodei says models will do most, maybe all, of what software engineers do end-to-end within six to twelve months. Not assisting. Not autocompleting. Handling the entire development process independently. If you are learning syntax today, you are learning a dead language. Amodei: “Then it’s a question of how fast does that loop close?” The loop is this. AI writes code. Code builds better AI. Better AI writes better code. Faster. Without sleep. Without the cognitive limits that cap how quickly any human engineer can work. Once that loop closes, technological progress stops being constrained by human output. It becomes self-sustaining. Exponential. Operating at a pace no human workforce can match or direct. Software engineering isn’t ending. It’s becoming supervision. The developers who survive won’t be the best coders. They’ll be the best supervisors. The ones who can direct AI output, catch its failures, and architect what it builds toward. The skill that matters stops being implementation. It becomes judgment. Most developers are still optimizing for a skillset about to become as obsolete as stenography. While the people who built the systems replacing them already stopped doing the work themselves. The window to develop that judgment before the loop closes is exactly as long as Amodei’s timeline. Six to twelve months.

Dustin

44,304 просмотров • 8 месяцев назад