Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

A DEVELOPER WALKED ON STAGE DRESSED AS A 1973 ENGINEER AND "PREDICTED" THE FUTURE OF PROGRAMMING. THE TWIST: EVERYTHING HE DESCRIBED WAS ALREADY INVENTED 40 YEARS EARLIER AND WE STILL REFUSE TO USE IT. 32 minutes from Bret Victor, doing the most quietly savage talk on our entire industry.... -> The idea that lands: we write code as step-by-step text instructions and call that "Just how programming is". He shows four better ways -- all discovered in the 60s and 70s, all abandoned. Manipulate the data directly instead of typing blind code. Tell the machine your goal instead of every tiny step. We saw all this, then walked away. Why? The moment you're sure you know what programming is, you stop seeing anything better. That certainty is the cage. And now AI is dragging us back to exactly what he begged for -- you describe the goal in plain words, the machine works out the how. The future he mourned is arriving anyway. You thought text files were just how code works. This is the talk that shows it was a choice, and maybe the wrong one. Watch this one. It'll ruin how you see your job ↓show more

slash1s

13,910 subscribers

688,447 Aufrufe • vor 3 Monaten •via X (Twitter)

Bildung Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

32 Kommentare

Profilbild von yourdudeness

yourdudenessvor 3 Monaten

He should’ve worn a short sleeve button up shirt to really sell it.

Profilbild von Henk Poley

Henk Poleyvor 3 Monaten

On YouTube:

Profilbild von hanna.ink base.eth

hanna.ink base.ethvor 3 Monaten

The bit where we act shocked by 50 year old ideas packaged as inonvation never gets old. Almost like the industry runs on amnesia by design

Profilbild von PrometheusRoot

PrometheusRootvor 3 Monaten

Genius. We think we are always so smart, but we know that people in the past were not. So this a genius way to show that we are still not that smart. Excelent take!

Profilbild von Medet Ahmetson

Medet Ahmetsonvor 3 Monaten

He is not a programmer, he is a UX designer whom I respect as that. His idea revolutionized in the 90s to visual programming and wysiwyg. But matters mental model not what users see. So it’s failed dead end or not solved properly.

Profilbild von MissileToe 🧟‍♂️

MissileToe 🧟‍♂️vor 3 Monaten

So fake. This is not history. Very sloppy use of some random facts with wishful thinking then shaming ‘future’ developers.

Profilbild von lagerskoy

lagerskoyvor 3 Monaten

The real lesson is that programming did not have to become walls of text, we just normalized the interface that won

Profilbild von TraderSven

TraderSvenvor 3 Monaten

This was also expressed in the days of "data driven" programming and "object oriented" programming. It was incorporated in a language named Prolog and several others in the past.

Profilbild von Phillip Lanos

Phillip Lanosvor 3 Monaten

lol when he started talking about API’s

Profilbild von Mark Szpakowski

Mark Szpakowskivor 3 Monaten

"Tell the machine your goal instead of every tiny step." This is also the current paradigm shift in biology (agency all the way down—cf @drmichaellevin) and what it implies for medicine: human-whispering—tell the body your goal instead of molecular micro-managing.

Profilbild von JoeInNJ

JoeInNJvor 3 Monaten

For those of you that remember the Shlaer-Mellor method...

Profilbild von hammertime

hammertimevor 3 Monaten

crazy how some of the "future of coding" was already figured out before the internet even existed

Profilbild von david powell

david powellvor 3 Monaten

yea the trap of early vonnuman arcitecture still in use today , lead to the single sequential thread of each core on multi core cpus , and the bit he missed , the bottelneck of memory bandwith over cpu access , the ditching of pipline proccessors used on some higher end mainframes in favor of simpler cpus a pipleine cpu for example one with say 8 stages , could do a log(cos(squre(a*b)/c))*sin(b*c)) as a single instruction , just data in and data out of the pipline , passing the intermediate values though the pipe without having to store or recall them individualy , ther just passed on to the next stage , saving quite a few memory read writes ( even at L1 chache ) , so rather than having say a 48core cpu , a single core with a programable 48 core recofigurable pipeline would have a significant performance advantage , but like he did say how to program it would be somthing that would not realy allow the use of legacy code or coding methods on half hybrid not fully fpga but partial confugurable pipline sub proccessors , passing data to the next after it did its little bit , on silicone where its timing is local to its core , as the distance accross the silicone adds a delay time , one that still affects the l1 cache read times , let alone actual system memory ,, theres a lot of room for improvment using primeraly ideas that where used in the 60's/70's that seemed to have been long forgoten in the name of refusal to learn and adopt new methods of programming , quite a valid talk

Profilbild von Gipp 🦅

Gipp 🦅vor 3 Monaten

he actually predicted the future

Profilbild von Enterprise Software Architecture

Enterprise Software Architecturevor 3 Monaten

👀 Too many mistakes, most likely intentional for comic effect, but I must admit, it is amusing. 🤭

Profilbild von Harry Tandy

Harry Tandyvor 3 Monaten

Bret Victor is a legend, this talk hurts

Profilbild von Anthology of Interest

Anthology of Interestvor 3 Monaten

There’s a lot of room for improvement for imperative programming already

Profilbild von Keenan Smith

Keenan Smithvor 3 Monaten

@andreasxirtus

Profilbild von Çağlar Araz

Çağlar Arazvor 3 Monaten

It is a continuous observation. AI idea has been there since 50's. So these observations are not shocking at all.

Profilbild von yhousegone

yhousegonevor 3 Monaten

>quietly >lands AI slop

Profilbild von shmidt

shmidtvor 3 Monaten

bret victor is unhinged in the best way, every talk hits different

Profilbild von HDP

HDPvor 3 Monaten

@0xKruger

Profilbild von cvxv666

cvxv666vor 3 Monaten

thx for sharing old gold stuff, saved this

Profilbild von Brent

Brentvor 3 Monaten

Actually far better than death by PowerPoint

Profilbild von Selim Tezel

Selim Tezelvor 3 Monaten

Yesterday's tomorrows. Brilliant. Thanks for sharing.

Profilbild von Robert

Robertvor 3 Monaten

I was there in 1973 and the ties were twice as wide and half as long as this guy’s

Profilbild von esp

espvor 3 Monaten

Brilliant

Profilbild von GenJeFT

GenJeFTvor 3 Monaten

@grok Hey Grok, Is the video in this tweet available on youtube?

Profilbild von Carolina Eslava. Comunicación Estratégica

Carolina Eslava. Comunicación Estratégicavor 3 Monaten

Thanks for sharing!!!

Profilbild von Maja Stanislawska🇵🇱🏳️‍⚧️

Maja Stanislawska🇵🇱🏳️‍⚧️vor 3 Monaten

he was some Erlang preacher, wasn't he?

Profilbild von Ridark

Ridarkvor 3 Monaten

Such a thoughtful pace throughout this conversation

Profilbild von Anthology of Interest

Anthology of Interestvor 3 Monaten

😭

Ähnliche Videos

IN A 1997 KEYNOTE A DEVELOPER TOLD A ROOM FULL OF PROGRAMMERS THAT THE COMPUTER REVOLUTION HAD NOT ACTUALLY HAPPENED YET. THEN HE PLAYED A CLIP OF WINDOWS, ICONS AND LIVE EDITING RUNNING ON A MACHINE FROM 1973 AND THE ROOM WENT QUIET. 62 minutes from Alan Kay -- the man who invented the word "object-oriented" and helped build the first modern personal computer at Xerox PARC. -> The idea that lands: almost everything you call "computing" is just paper, digitized. Documents, mail, folders. We took the most powerful medium ever made and used it to imitate the office. The real machine -- the one that thinks with you, that you shape live instead of typing at -- was sketched in the 60s and 70s, then quietly abandoned. He calls modern software an Egyptian pyramid: millions of bricks stacked by brute force, no structure underneath. And now AI is quietly hauling us back toward what he wanted -- you describe intent, the machine builds the how. Not a revolution from nowhere. A return to a dream we walked away from. You thought this was the future. This is the talk that shows you it is a detour we have been on for 40 years. Save this. It reframes the whole industry ↓

IN A 1997 KEYNOTE A DEVELOPER TOLD A ROOM FULL OF PROGRAMMERS THAT THE COMPUTER REVOLUTION HAD NOT ACTUALLY HAPPENED YET. THEN HE PLAYED A CLIP OF WINDOWS, ICONS AND LIVE EDITING RUNNING ON A MACHINE FROM 1973 AND THE ROOM WENT QUIET. 62 minutes from Alan Kay -- the man who invented the word "object-oriented" and helped build the first modern personal computer at Xerox PARC. -> The idea that lands: almost everything you call "computing" is just paper, digitized. Documents, mail, folders. We took the most powerful medium ever made and used it to imitate the office. The real machine -- the one that thinks with you, that you shape live instead of typing at -- was sketched in the 60s and 70s, then quietly abandoned. He calls modern software an Egyptian pyramid: millions of bricks stacked by brute force, no structure underneath. And now AI is quietly hauling us back toward what he wanted -- you describe intent, the machine builds the how. Not a revolution from nowhere. A return to a dream we walked away from. You thought this was the future. This is the talk that shows you it is a detour we have been on for 40 years. Save this. It reframes the whole industry ↓

slash1s

294,844 Aufrufe • vor 3 Monaten

IN 1986 MIT FILMED THE LECTURE WHERE CODE STOPPED BEING CODE AND BECAME DATA 43 minutes from Gerald Sussman, in the most legendary intro programming course ever recorded. -> The idea that lands: to a program, your code is just data it can read and rewrite. He builds a program that does real calculus -- not by crunching numbers, but by reading the math as a list and transforming it piece by piece. Then he shows the trick hiding under all of it: in this language, code and data are the same material. Forty years later that is exactly what an AI coding agent is -- a program that reads your code as data, rewrites it, and hands it back. Sussman drew the whole idea on a blackboard in 1986. Writing code was never the deepest skill -- understanding that code itself is data a program can manipulate is. This is where you learn it. Most people think AI writing code is brand new. The ones who watch this saw the blueprint 40 years ago. Bookmark & Watch it. This one's a legend ↓

slash1s

22,107 Aufrufe • vor 3 Monaten

IN 1982 GRACE HOPPER WALKED INTO THE NSA AND EXPLAINED THE NEXT 40 YEARS OF COMPUTING 48 minutes from the woman who invented the compiler -- the first person who made a machine understand human words. -> The idea that lands: stop bending humans to the machine. Bend the machine to humans. She built the first compiler when the experts swore computers could only crunch numbers. She wanted you to write in plain words and let the machine handle the translation. Forty years later you barely write code at all -- you tell the model what you want in plain English and it writes it for you. The compiler was step one. The LLM is the same idea, finished. Memorizing syntax was never the skill -- saying clearly what you actually want is. This is where that idea was born. Most people think talking to your computer in plain English started in 2023. The ones who watch this know a Navy admiral called it in 1982. Bookmark & Watch it today ↓

IN 1982 GRACE HOPPER WALKED INTO THE NSA AND EXPLAINED THE NEXT 40 YEARS OF COMPUTING 48 minutes from the woman who invented the compiler -- the first person who made a machine understand human words. -> The idea that lands: stop bending humans to the machine. Bend the machine to humans. She built the first compiler when the experts swore computers could only crunch numbers. She wanted you to write in plain words and let the machine handle the translation. Forty years later you barely write code at all -- you tell the model what you want in plain English and it writes it for you. The compiler was step one. The LLM is the same idea, finished. Memorizing syntax was never the skill -- saying clearly what you actually want is. This is where that idea was born. Most people think talking to your computer in plain English started in 2023. The ones who watch this know a Navy admiral called it in 1982. Bookmark & Watch it today ↓

slash1s

61,013 Aufrufe • vor 3 Monaten

Larry Ellison just told every software engineer on Earth their job description is dead. Not evolving. Dead. Ellison: “The code that Oracle is writing, Oracle isn’t writing. Our AI models are writing.” This is not a startup demo. This is one of the largest infrastructure monopolies on the planet telling you it already replaced the people who built it. For fifty years, building software meant translating human intent into machine instructions. Line by line. Bug by bug. Sprint by sprint. That entire layer is gone. Ellison: “We don’t write the procedure. We declare our intent.” That sentence just made the entire engineering labor market flinch. The procedure was the job. The procedure was the paycheck. The procedure was what made a developer valuable. And now the machine does it without being asked twice. Ellison: “We just tell the model what we want the program to do, and then the AI comes up with a step-by-step process to actually do it.” You are no longer paid to build. You are paid to think. And most organizations have no idea how to evaluate that. The companies still hiring armies of developers to grind through codebases are paying salaries the machine already made worthless. Not in years. In seconds. When a company worth hundreds of billions hands the keyboard to the machine and tells you the output is better, the debate is not winding down. The debate is over. The enterprise that wins this decade does not write the best code. It removes the human from the process entirely and runs on intent alone. The programmers who survive are the ones who realize the craft is no longer typing. It is architecture. It is judgment. It is knowing what to build and why. Everything else now belongs to the machine. And the machine does not negotiate severance.

Larry Ellison just told every software engineer on Earth their job description is dead. Not evolving. Dead. Ellison: “The code that Oracle is writing, Oracle isn’t writing. Our AI models are writing.” This is not a startup demo. This is one of the largest infrastructure monopolies on the planet telling you it already replaced the people who built it. For fifty years, building software meant translating human intent into machine instructions. Line by line. Bug by bug. Sprint by sprint. That entire layer is gone. Ellison: “We don’t write the procedure. We declare our intent.” That sentence just made the entire engineering labor market flinch. The procedure was the job. The procedure was the paycheck. The procedure was what made a developer valuable. And now the machine does it without being asked twice. Ellison: “We just tell the model what we want the program to do, and then the AI comes up with a step-by-step process to actually do it.” You are no longer paid to build. You are paid to think. And most organizations have no idea how to evaluate that. The companies still hiring armies of developers to grind through codebases are paying salaries the machine already made worthless. Not in years. In seconds. When a company worth hundreds of billions hands the keyboard to the machine and tells you the output is better, the debate is not winding down. The debate is over. The enterprise that wins this decade does not write the best code. It removes the human from the process entirely and runs on intent alone. The programmers who survive are the ones who realize the craft is no longer typing. It is architecture. It is judgment. It is knowing what to build and why. Everything else now belongs to the machine. And the machine does not negotiate severance.

Dustin

536,629 Aufrufe • vor 6 Monaten

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anthropic Claude Code engineer: "The moment you're reviewing every line Claude writes, you became its tester. You weren't hired for that." this 36 min talk is the clearest breakdown of how to get yourself out of the loop entirely the shift is simple: you stop prompting and start building agents that work instead of you agents that run, check themselves, and keep going while your laptop is closed watch it, then build your own with the step-by-step guide below

Anatoli Kopadze

28,042 Aufrufe • vor 3 Monaten

THE ENGINE DIRECTOR BEHIND AAA CONSOLE GAMES WALKED ON STAGE AT A C++ CONFERENCE AND TOLD A ROOM OF EXPERTS THAT THE CLEAN, OBJECT ORIENTED CODE THEY ARE PROUD OF IS A LIE AND IT QUIETLY THROWS AWAY 90% OF THE MACHINE THEY PAID FOR 85 minutes from Mike Acton -- engine director at Insomniac Games, where wasting cycles is not an abstract debate, it is the difference between a game that ships and one that dies. -> His first principle is blunt: the only purpose of any program is to transform data. Not to model the world in pretty classes. Move data, fast. 06:33 -- The lie he calls out: "Software is the platform". No. The hardware is the platform. Ignore it and you cannot even reason about the cost of your own code. Most devs never look at what the CPU actually does. They stack abstractions until the machine spends its life waiting on memory it should never have touched. 49:38 -- He prints a value, zips it, and measures the waste directly. A brutal little trick that exposes how much of your data is pure noise. And this is the AI era's blind spot too. Agents generate more abstract code faster, on hardware nobody profiles, while the GPU bill quietly explodes. You thought clean code was the goal. This is the man shipping real engines saying the machine is the goal, and clean code is often how you lose it. Bookmark it & you'll never look at your own abstractions the same ↓

THE ENGINE DIRECTOR BEHIND AAA CONSOLE GAMES WALKED ON STAGE AT A C++ CONFERENCE AND TOLD A ROOM OF EXPERTS THAT THE CLEAN, OBJECT ORIENTED CODE THEY ARE PROUD OF IS A LIE AND IT QUIETLY THROWS AWAY 90% OF THE MACHINE THEY PAID FOR 85 minutes from Mike Acton -- engine director at Insomniac Games, where wasting cycles is not an abstract debate, it is the difference between a game that ships and one that dies. -> His first principle is blunt: the only purpose of any program is to transform data. Not to model the world in pretty classes. Move data, fast. 06:33 -- The lie he calls out: "Software is the platform". No. The hardware is the platform. Ignore it and you cannot even reason about the cost of your own code. Most devs never look at what the CPU actually does. They stack abstractions until the machine spends its life waiting on memory it should never have touched. 49:38 -- He prints a value, zips it, and measures the waste directly. A brutal little trick that exposes how much of your data is pure noise. And this is the AI era's blind spot too. Agents generate more abstract code faster, on hardware nobody profiles, while the GPU bill quietly explodes. You thought clean code was the goal. This is the man shipping real engines saying the machine is the goal, and clean code is often how you lose it. Bookmark it & you'll never look at your own abstractions the same ↓

slash1s

174,339 Aufrufe • vor 2 Monaten

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓

slash1s

386,685 Aufrufe • vor 4 Monaten

ONE OF THE MINDS BEHIND JAVA GAVE A LECTURE WHERE HE BANNED HIMSELF FROM USING ANY BIG WORD UNTIL HE DEFINED IT FIRST AND IN DOING SO QUIETLY EXPLAINED HOW EVERY GREAT SYSTEM GETS BUILT A talk from Guy Steele -- co-author of the Java spec and a designer of Scheme -- where the form of the talk is the lesson. -> The moment you catch what he's doing, it rewires you. He starts with only the smallest words, then builds every larger idea live, in front of you, from the pieces he already gave you. The talk grows its own vocabulary as it goes. That's the whole secret of language and system design he's smuggling in: you don't ship something huge and finished. You ship a small core and the means to grow it. Miss that and you spend your career fighting your own tools. Memorizing a language was never the skill -> understanding how a good one is meant to grow is. And as AI starts generating the primitives you build on, knowing what makes a foundation extensible instead of brittle is the entire game. Twenty-five years on, language designers still point to this talk as the cleanest demonstration of the idea ever performed. Bookmark it & Watch how he builds the whole thing from nothing ↓

ONE OF THE MINDS BEHIND JAVA GAVE A LECTURE WHERE HE BANNED HIMSELF FROM USING ANY BIG WORD UNTIL HE DEFINED IT FIRST AND IN DOING SO QUIETLY EXPLAINED HOW EVERY GREAT SYSTEM GETS BUILT A talk from Guy Steele -- co-author of the Java spec and a designer of Scheme -- where the form of the talk is the lesson. -> The moment you catch what he's doing, it rewires you. He starts with only the smallest words, then builds every larger idea live, in front of you, from the pieces he already gave you. The talk grows its own vocabulary as it goes. That's the whole secret of language and system design he's smuggling in: you don't ship something huge and finished. You ship a small core and the means to grow it. Miss that and you spend your career fighting your own tools. Memorizing a language was never the skill -> understanding how a good one is meant to grow is. And as AI starts generating the primitives you build on, knowing what makes a foundation extensible instead of brittle is the entire game. Twenty-five years on, language designers still point to this talk as the cleanest demonstration of the idea ever performed. Bookmark it & Watch how he builds the whole thing from nothing ↓

slash1s

358,660 Aufrufe • vor 4 Monaten

IF YOU ARE STILL PROMPTING BY HAND IN 2026 YOU ARE ALREADY BEHIND the guy who built Claude Code at Anthropic said he stopped writing prompts a long time ago he runs loops instead, systems that write the prompts for him and keep working while he sleeps you type one request at a time and wait for the answer he built a machine that fires hundreds of requests, checks its own output and fixes itself with no hands on the keyboard here is how you make the jump step 1 stop treating the model like a chat box and start treating it like a worker you manage step 2 write a loop that takes a goal, breaks it into tasks and sends each one to the model on its own step 3 add a second pass where the model grades its own work and retries whatever failed step 4 let it run on a timer so it keeps shipping while you are away from the screen the person still typing prompts one by one is doing the work of a intern the person running loops is doing the work of a whole team off one laptop prompting was never the skill, building the system that prompts for you is

IF YOU ARE STILL PROMPTING BY HAND IN 2026 YOU ARE ALREADY BEHIND the guy who built Claude Code at Anthropic said he stopped writing prompts a long time ago he runs loops instead, systems that write the prompts for him and keep working while he sleeps you type one request at a time and wait for the answer he built a machine that fires hundreds of requests, checks its own output and fixes itself with no hands on the keyboard here is how you make the jump step 1 stop treating the model like a chat box and start treating it like a worker you manage step 2 write a loop that takes a goal, breaks it into tasks and sends each one to the model on its own step 3 add a second pass where the model grades its own work and retries whatever failed step 4 let it run on a timer so it keeps shipping while you are away from the screen the person still typing prompts one by one is doing the work of a intern the person running loops is doing the work of a whole team off one laptop prompting was never the skill, building the system that prompts for you is

Atlas

16,641 Aufrufe • vor 1 Monat

YOU BETTER STOP DOING EVERYTHING RIGHT NOW Y’all….. This is just worth your time and you better watch it twice!! Two for Tuesday!! This cat sees something in the sky that just looks all wrong… He begins to record and he tells you everything that is happening like a sports announcer… Watch this!!! This is what he captured…..

YOU BETTER STOP DOING EVERYTHING RIGHT NOW Y’all….. This is just worth your time and you better watch it twice!! Two for Tuesday!! This cat sees something in the sky that just looks all wrong… He begins to record and he tells you everything that is happening like a sports announcer… Watch this!!! This is what he captured…..

Eddie Abbott

212,742 Aufrufe • vor 3 Monaten

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

slash1s

193,107 Aufrufe • vor 4 Monaten

IN 1999 MIT FILMED A MATH LECTURE THAT QUIETLY BECAME THE FOUNDATION OF EVERY AI MODEL YOU'VE EVER USED AND ALMOST NO ONE WAS TAUGHT TO SEE IT THAT WAY 39 minutes from Gilbert Strang, who taught this at MIT for over 60 years -- the linear algebra course an entire generation of engineers and data scientists grew up on. -> The shift it creates: you stop seeing matrices as boring grids of numbers and start seeing them as the language of space, data, and motion itself. School drilled you to crunch matrices by hand and never told you why. Strang shows you what they actually mean. Every neural net, every embedding, every model you prompt is linear algebra running underneath. The math you skipped is the engine of the thing you use all day. Memorizing the steps was never the skill -> seeing what the numbers do is. This is where it finally clicks. Most people fear linear algebra and move on. The ones who watched this see straight into how AI actually works. Bookmark & Watch it today, this one's a legend ↓

IN 1999 MIT FILMED A MATH LECTURE THAT QUIETLY BECAME THE FOUNDATION OF EVERY AI MODEL YOU'VE EVER USED AND ALMOST NO ONE WAS TAUGHT TO SEE IT THAT WAY 39 minutes from Gilbert Strang, who taught this at MIT for over 60 years -- the linear algebra course an entire generation of engineers and data scientists grew up on. -> The shift it creates: you stop seeing matrices as boring grids of numbers and start seeing them as the language of space, data, and motion itself. School drilled you to crunch matrices by hand and never told you why. Strang shows you what they actually mean. Every neural net, every embedding, every model you prompt is linear algebra running underneath. The math you skipped is the engine of the thing you use all day. Memorizing the steps was never the skill -> seeing what the numbers do is. This is where it finally clicks. Most people fear linear algebra and move on. The ones who watched this see straight into how AI actually works. Bookmark & Watch it today, this one's a legend ↓

slash1s

435,509 Aufrufe • vor 3 Monaten

.Oprah Winfrey: For all of you watching who are still on the fence, in the middle, independent as I am, or whether you just still don't know what you're gonna do. This is the moment for all decent and caring people who want the best for yourself and other people. This is the moment for people who are tired of all of the bickering and all of the name-calling, people who are exhausted by the craziness and the made up stories and the conspiracies. This is the moment you wanna get on with your life because you know that we can do better and that we deserve better. You know this, I know you know this, I know you feel this. I know this is what you're saying amongst yourselves. We're better than this. And as my friend and mentor Maya Angelou always said, ‘When you know better, you got to do better.’ So let's do better and vote for Kamala Harris

.Oprah Winfrey: For all of you watching who are still on the fence, in the middle, independent as I am, or whether you just still don't know what you're gonna do. This is the moment for all decent and caring people who want the best for yourself and other people. This is the moment for people who are tired of all of the bickering and all of the name-calling, people who are exhausted by the craziness and the made up stories and the conspiracies. This is the moment you wanna get on with your life because you know that we can do better and that we deserve better. You know this, I know you know this, I know you feel this. I know this is what you're saying amongst yourselves. We're better than this. And as my friend and mentor Maya Angelou always said, ‘When you know better, you got to do better.’ So let's do better and vote for Kamala Harris

Headquarters

2,490,687 Aufrufe • vor 2 Jahren

Coinbase CEO Explains “Reverse Prompting” and the Rise of the AI CEO Brian Armstrong: “One of the big pushes we made in the last year was we got our own internal hosted AI model that was connected to all of our data sources, right?” “So it's like every Slack message, every Google doc, Salesforce data, Confluence, you know.” “So now the data is all aggregated and I've started to ask it really… it's not just like prompting it, ‘Hey, can you write this kind of memo for me,’ or something.” “I'm asking these AI agents now, ‘As CEO, what should I be aware of in the company that I might not be aware of?’ And it'll tell me, ‘Did you know that there's actually disagreement on this team about the strategy?’ And I was like, actually, I didn't know that.” “This is like reverse prompting. So instead of telling the AI agent what you want it to do, you ask it what you should be thinking more about.” @jason: “It's a mentor. It's a coach.” Brian: “Yeah. Like, what could make me a better CEO? And it's like, ‘Well, I looked at how you spent your time in the last quarter and here's how you said that you wanted to spend it, but you actually spent 32% of your time on this instead of 20%.’” “I've asked it other questions like, ‘What's the thing that I changed my mind on the most over the last year?’ Things like that.” “It'll prompt you with information you should be thinking about instead of the other way around.” Thanks to our partner for making this happen!: Our episode is sponsored by the New York Stock Exchange - a modern marketplace and exchange for building the future. It all happens at the NYSE 🏛.

Coinbase CEO Explains “Reverse Prompting” and the Rise of the AI CEO Brian Armstrong: “One of the big pushes we made in the last year was we got our own internal hosted AI model that was connected to all of our data sources, right?” “So it's like every Slack message, every Google doc, Salesforce data, Confluence, you know.” “So now the data is all aggregated and I've started to ask it really… it's not just like prompting it, ‘Hey, can you write this kind of memo for me,’ or something.” “I'm asking these AI agents now, ‘As CEO, what should I be aware of in the company that I might not be aware of?’ And it'll tell me, ‘Did you know that there's actually disagreement on this team about the strategy?’ And I was like, actually, I didn't know that.” “This is like reverse prompting. So instead of telling the AI agent what you want it to do, you ask it what you should be thinking more about.” @jason: “It's a mentor. It's a coach.” Brian: “Yeah. Like, what could make me a better CEO? And it's like, ‘Well, I looked at how you spent your time in the last quarter and here's how you said that you wanted to spend it, but you actually spent 32% of your time on this instead of 20%.’” “I've asked it other questions like, ‘What's the thing that I changed my mind on the most over the last year?’ Things like that.” “It'll prompt you with information you should be thinking about instead of the other way around.” Thanks to our partner for making this happen!: Our episode is sponsored by the New York Stock Exchange - a modern marketplace and exchange for building the future. It all happens at the NYSE 🏛.

The All-In Podcast

80,524 Aufrufe • vor 8 Monaten

A DEVELOPER STOOD UP AT A CONFERENCE AND APOLOGIZED TO THE ENTIRE INDUSTRY FOR ONE LINE OF CODE HE WROTE IN 1965. THAT SINGLE DECISION HAS SINCE CAUSED CRASHES, BREACHES AND ROUGHLY A BILLION DOLLARS OF DAMAGE AND YOU HIT IT EVERY SINGLE DAY 61 minutes from Tony Hoare -- the man who invented quicksort, won the Turing Award, and passed away in early 2026, leaving this as one of his most honest talks. -> His confession: he added the null reference, letting any variable secretly mean "nothing", simply because it was easy to implement. That one shortcut became the null pointer, the undefined, the None -- the crash waiting inside almost every program ever written. He calls it his billion-dollar mistake, and he is not exaggerating. Whole classes of bugs and security holes trace straight back to it. And this is the deeper lesson under the AI rush: the easy shortcut you ship today becomes the landmine everyone steps on for the next 40 years. You thought null was just part of how code works. This is the talk where the man who made it tells you it never had to be. Bookmark & Watch this one. You'll never type null the same way ↓

A DEVELOPER STOOD UP AT A CONFERENCE AND APOLOGIZED TO THE ENTIRE INDUSTRY FOR ONE LINE OF CODE HE WROTE IN 1965. THAT SINGLE DECISION HAS SINCE CAUSED CRASHES, BREACHES AND ROUGHLY A BILLION DOLLARS OF DAMAGE AND YOU HIT IT EVERY SINGLE DAY 61 minutes from Tony Hoare -- the man who invented quicksort, won the Turing Award, and passed away in early 2026, leaving this as one of his most honest talks. -> His confession: he added the null reference, letting any variable secretly mean "nothing", simply because it was easy to implement. That one shortcut became the null pointer, the undefined, the None -- the crash waiting inside almost every program ever written. He calls it his billion-dollar mistake, and he is not exaggerating. Whole classes of bugs and security holes trace straight back to it. And this is the deeper lesson under the AI rush: the easy shortcut you ship today becomes the landmine everyone steps on for the next 40 years. You thought null was just part of how code works. This is the talk where the man who made it tells you it never had to be. Bookmark & Watch this one. You'll never type null the same way ↓

slash1s

282,239 Aufrufe • vor 3 Monaten

Darko on Brandon Ingram’s defence improving over the season: “Everything started in the Summer League. When he saw our summer league team play and how they were aggressive, he was like, ‘whoa.’ He was impressed there and he took it very seriously; that he needs to step up on that side of the floor.” “What I can tell you about Brandon Ingram is that, he’s an absolute team guy, and he’s an absolute winner. All he wants to do is win. If that demands to step out on the defensive end, he’s not shying away from there.” “He’s doing an outstanding job for us defensively, and we want him to be 1% better for the next game.”

Darko on Brandon Ingram’s defence improving over the season: “Everything started in the Summer League. When he saw our summer league team play and how they were aggressive, he was like, ‘whoa.’ He was impressed there and he took it very seriously; that he needs to step up on that side of the floor.” “What I can tell you about Brandon Ingram is that, he’s an absolute team guy, and he’s an absolute winner. All he wants to do is win. If that demands to step out on the defensive end, he’s not shying away from there.” “He’s doing an outstanding job for us defensively, and we want him to be 1% better for the next game.”

Omer Osman

34,198 Aufrufe • vor 9 Monaten

“Hell Isn’t a place”. If you think Heaven is a place you go when you die, you’ve missed the whole point of being alive! Jesus said the Kingdom of Heaven is within you! He didn’t say its in the clouds. He didn’t say it’s coming someday in the future if you behave. He said it’s in you, right now! Which means Heaven isn’t a destination, it’s a decision. We create Heaven or hell in real time by how we act, how we think, how we live, how we love ❤️! And one of the greatest traps of religion and cultures is that heaven is somewhere out there, the sky, in the future after we die. but it is within us. God gave us a canvas, what we paint on it is up to us! Do you wanna wait for Heaven? Or do you want to build it? He gave you the breath, He gave you the will, He gave you the Divine Spark to observe, assign meaning, and create! That’s what God does and He gave us the same power! “

“Hell Isn’t a place”. If you think Heaven is a place you go when you die, you’ve missed the whole point of being alive! Jesus said the Kingdom of Heaven is within you! He didn’t say its in the clouds. He didn’t say it’s coming someday in the future if you behave. He said it’s in you, right now! Which means Heaven isn’t a destination, it’s a decision. We create Heaven or hell in real time by how we act, how we think, how we live, how we love ❤️! And one of the greatest traps of religion and cultures is that heaven is somewhere out there, the sky, in the future after we die. but it is within us. God gave us a canvas, what we paint on it is up to us! Do you wanna wait for Heaven? Or do you want to build it? He gave you the breath, He gave you the will, He gave you the Divine Spark to observe, assign meaning, and create! That’s what God does and He gave us the same power! “

The Core

11,192 Aufrufe • vor 29 Tagen

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Boris Cherny, the creator of Claude Code at Anthropic, just explained why he stopped prompting Claude entirely in this talk he breaks down exactly how the future is teams of agents, not better prompts: - the 14% you lose to CLAUDE.md before typing a word - the features that change how Claude thinks before you type a word - the features most Claude users don't know exist - why typing prompts one at a time is already the slow lane Boris Cherny: "Now I don’t prompt Claude anymore - I have loops that are running. My job is to write loops." if you've been using Claude for more than a month and never left the chat window, you have at least 23 untouched features. probably 25 instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed my breakdown of all 25 features is below

Khairallah AL-Awady

103,180 Aufrufe • vor 4 Monaten

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

1,309,179 Aufrufe • vor 4 Monaten

Church, why are we celebrating or partaking in ANYTHING on October 31st? Ask yourself, how is anything you are doing on that day honoring God? We are in this world church, not of it. We are commanded to know our enemy and know what he is doing in this evil world. Unfortunately ALL of our “holidays” have pagan roots because satan is the god of this world and it is his desire- every single second of every single day- to drive you and your family away from Christ and away from the Word.

Church, why are we celebrating or partaking in ANYTHING on October 31st? Ask yourself, how is anything you are doing on that day honoring God? We are in this world church, not of it. We are commanded to know our enemy and know what he is doing in this evil world. Unfortunately ALL of our “holidays” have pagan roots because satan is the god of this world and it is his desire- every single second of every single day- to drive you and your family away from Christ and away from the Word.

Ashley Hays

31,377 Aufrufe • vor 11 Monaten