Loading video...

Video Failed to Load

Go Home

Karpathy just defined the 3 ways you're going to code for the next decade which one you choose determines your salary > Zero AI - writing every line from scratch. pure artisan, very slow > Copilot mode - you're the architect, AI is the autocomplete. where most seniors live...

11,342 views • 2 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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,325 views • 6 months ago

Jordan Peterson: "If you're competent and silent you will be ignored." "You might think well people should reward you because you're competent. And yes of course they should. But if you're competent and silent then you're just part of the background that's keeping everything functioning" On why you cannot negotiate from a position of weakness: "If you want to push your career forward you have to push it forward. You have to be competent and you have to be strategic" "To be strategic when you negotiate for a new position or a new salary you have to be able to say if you don't give me what I want then something you don't like will happen to you" "It's not a physical threat. It's that you have an option" "You have your CV in order. You're educated and competent and desirable to people outside of your immediate job. You're willing to instantly put yourself on the job market" "So that when you go talk to the person you're negotiating with you're credible" On the one thing most people completely miss about negotiation: "It's very seldom that you're talking to the person who's at the top of the pecking order. What you need to do is tell them a story that they can tell to their boss to make you not a problem" "A good story is look we really need this person because they're hyper competent and they have a better offer" "If you go in there with no power you're going to lose. Obviously" He concludes with the one thing every competent person needs to hear: "The first thing you need to know if you're going to negotiate is that you have to be able to say no. And what no means is that you're not going to do it"

Brad

34,992 views • 18 days ago