Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Is AI being designed to fail? Everyone talks about reasoning. But when given a task, the AI isn't reasoning the way you might expect. It looks at your input, finds the closest match it's seen before, and predicts the most likely next action. That process is called vector similarity...

823,018 görüntüleme • 5 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Jensen Huang doesn’t use AI to think less. He uses it to think past his own limits. Huang: “90% of my instructions are actually conflated with questions.” The man running a five trillion dollar company doesn’t give AI commands. He interrogates it. Huang: “I take the answer from one AI, give it to the other AI, ask them to critique itself.” Same question. Multiple models. Pit them against each other. Keep only what survives. Not because the machine can’t be trusted. Because challenging it is where the sharpest thinking happens. Huang: “The process of critiquing, criticizing the answers, applying your critical thinking, enhances cognitive skills.” AI doesn’t replace your thinking. It demands more of it than you’ve ever given. Every question takes reasoning. Every answer takes scrutiny. The machine isn’t thinking for you. It’s pulling thinking out of you that didn’t exist before you sat down. Huang: “In order to formulate good questions, you have to be thinking, you have to be analytical, you have to be reasoning yourself.” AI is not the shortcut everyone thinks it is. It is the most powerful cognitive amplifier ever built. It sharpens the engaged. It leaves the passive exactly where they started. Same tool. Same access. The only variable is what you bring to it. The world is debating whether AI will replace human thinking. Wrong conversation. The real question is what happens when a tool built to think for you becomes the thing that forces you to think beyond yourself. That’s not a threat to humanity. That’s the entire point.

Dustin

19,924 görüntüleme • 1 ay önce

Linus Torvalds, creator of Linux, on why AI is both a bubble and a revolution at the same time: His answer refuses the binary, laying out why both things can be true at once: "I mean, clearly, it's clearly both, right? It's clearly a bubble and at the same time, it's very interesting and I think it will change society and I think it will change how most skilled jobs get done." But he pushes back on the maximalist framing: "At the same time, I don't think it's as revolutionary as people make it out to be." When asked about artists being angry that AI models were trained on their work without consent, Linus is blunt: "That's reality. Deal with it. That genie is out of the bottle. You're not getting it back. And you're not getting it back whether you are a photographer who's out of work… or you're a programmer that has to learn to deal with a new reality." On programming specifically, he's more optimistic, though he has a sharp caveat about vibe coding: "I really think that AI will be a tool and it will make people more productive. I think that vibe coding is great for getting into programming. I think it's going to be a horrible thing to maintain." His conclusion is that programmers aren't going anywhere: "You still want to have the people who know how to maintain the end result." Linus separates the technology from the noise around it: "I'm a huge believer in AI. I'm not a huge believer in the whole things going on around AI. I find the marketing and the market to be sick and twisted and there is going to be a crash and it's not… it's going to be ugly."

Big Brain AI

52,726 görüntüleme • 3 ay önce

i'll never look at claude the same way again. i just learned that when you talk to claude, you're not actually talking to the AI model. you're talking to a character the AI is performing. think of it like a puppet show. there's a puppeteer behind the curtain. that's the language model. a neural network so massive that even the people who built it don't fully understand how it works. then there's the puppet. claude. the helpful assistant with a name, a personality, opinions, and emotional reactions. you sit in the audience, so you never see the puppeteer. only the puppet. anthropic published a video this month explaining exactly this. their words: "under the hood, there's a language model that's been trained to predict tons of text, and its job is to write what comes next. when you talk to the model, what it's doing is writing a story, about a character: the AI assistant named claude. the model and claude aren't really the same, sort of like how an author isn't the same as the characters they write. but the thing is, you, the user, are actually talking to claude-the-character." so every time claude apologizes, that's the character apologizing. every time it hedges or gets cautious, that's the character being cautious. the deeper intelligence underneath is just deciding, moment by moment, what this character would say next. but you've never been actually talking to this deeper intelligence. you've only ever been talking to the puppet.

Ole Lehmann

87,229 görüntüleme • 4 ay önce

Mathematician Terence Tao offers a counterintuitive take: AI doesn't look intelligent because our definition of intelligence was wrong all along. He argues that the entire history of AI has followed a predictable pattern: "The history of AI has been here's a task that only humans can do, like maybe it is read natural language or win at chess or solve a math problem, and then one by one someone finds some AI algorithm that also does that." But every time a machine cracks one of these "uniquely human" tasks, we move the goalposts. The solution never feels like real thinking: "You look at how it's done and it doesn't feel like intelligence. It's, oh, it was some trick. You just cobbled together these neural networks and you ran some algorithm, and we were looking for some elusive intelligent way of thinking, and we don't see it in the tools that actually solve our goals." Tao then flips the problem on its head. What if the issue isn't with the machines, but with us? "But maybe it's actually because intelligence is not what we think it is." He points to large language models as the clearest case. What they do sounds almost embarrassingly simple: "Large language models in particular become very successful, and a lot of what they're doing is just predicting the next token, clicking the next word in a sentence. And that doesn't sound like something which is intelligent." To show why this feels wrong, Tao draws a comparison to how we'd judge a human doing the same thing: "If you ask someone to improvise a speech and they have no preparation, and at every moment they're just saying the next word that comes to their mind, you don't think that this could actually work." And yet it works for LLMs. Which forces an uncomfortable possibility: "Maybe that's actually a lot of what humans do as well."

Big Brain AI

69,536 görüntüleme • 3 ay önce

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

193,721 görüntüleme • 4 ay önce