正在加载视频...

视频加载失败

返回首页

A DEVELOPER WHO HELPS MAINTAIN GIT ITSELF PROVED THAT USING GIT AND CONTRIBUTING WITH GIT ARE TWO DIFFERENT SKILLS AND ALMOST NO ONE LEARNS THE SECOND 55 minutes from Johannes Schindelin, one of git's most prolific contributors, on the workflow that gets your code accepted into a project you...

slash1sol's profile picture

slash1s

9,536 subscribers

12,624 次观看 • 23 天前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓
31:26

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓

slash1s

255,565 次观看 • 27 天前

A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, Git stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. git add and git commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was Git hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when Git breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓
55:19

A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, Git stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. git add and git commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was Git hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when Git breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

slash1s

236,545 次观看 • 1 个月前

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓
32:07

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

slash1s

37,628 次观看 • 23 天前

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is __init__, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓
27:10

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is __init__, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓

slash1s

266,884 次观看 • 19 天前

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓
1:24:59

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓

slash1s

456,111 次观看 • 28 天前

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓
1:01:03

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓

slash1s

13,073 次观看 • 22 天前

HARVARD RELEASED A 65-MIN MASTERCLASS ON GIT & GITHUB BECAUSE VIBE-CODERS STILL DON'T KNOW HOW TO COMMIT 1 hour and 5 minutes of raw, no-nonsense version control architecture from the creators of CS50. -> The moment you watch it, you realize why most modern developers are breaking their production branches. Every tier-1 tech company is now filtering candidates who can't handle basic merge conflicts. Git isn't a "nice-to-know" anymore -> it's compliance. Your AI can write the code. That wasn't the problem. The problem is you don't know how to merge it without breaking the repo. Don’t forget to bookmark it.
1:05:58

HARVARD RELEASED A 65-MIN MASTERCLASS ON GIT & GITHUB BECAUSE VIBE-CODERS STILL DON'T KNOW HOW TO COMMIT 1 hour and 5 minutes of raw, no-nonsense version control architecture from the creators of CS50. -> The moment you watch it, you realize why most modern developers are breaking their production branches. Every tier-1 tech company is now filtering candidates who can't handle basic merge conflicts. Git isn't a "nice-to-know" anymore -> it's compliance. Your AI can write the code. That wasn't the problem. The problem is you don't know how to merge it without breaking the repo. Don’t forget to bookmark it.

slash1s

251,459 次观看 • 1 个月前

AN MIT RESEARCHER PROVED GIT ISN'T HARD BECAUSE YOU'RE BAD AT IT -- IT'S HARD BECAUSE IT WAS DESIGNED THAT WAY 27 minutes from a PhD researcher in MIT's Software Design Group, using actual design theory to show why the tool that confuses everyone confuses everyone for a reason. -> The moment it lands, years of feeling stupid evaporate. The gap between what git's commands say and what they actually do was never in your head. It's baked into the tool. He maps the difference between what you think a command does and what git really does underneath. Once you see that gap, the confusion finally has a name and it stops being yours to carry. Struggling with git was never a skills issue -> it's a design issue, and knowing where the model lies to you is what turns panic into control. And as AI agents fire off commits and rebases you didn't write, the person who understands where git misleads is the one who untangles the mess. You were never bad at git. You were just never shown where it was built to trip you. Bookmark & Watch it today ↓
26:35

AN MIT RESEARCHER PROVED GIT ISN'T HARD BECAUSE YOU'RE BAD AT IT -- IT'S HARD BECAUSE IT WAS DESIGNED THAT WAY 27 minutes from a PhD researcher in MIT's Software Design Group, using actual design theory to show why the tool that confuses everyone confuses everyone for a reason. -> The moment it lands, years of feeling stupid evaporate. The gap between what git's commands say and what they actually do was never in your head. It's baked into the tool. He maps the difference between what you think a command does and what git really does underneath. Once you see that gap, the confusion finally has a name and it stops being yours to carry. Struggling with git was never a skills issue -> it's a design issue, and knowing where the model lies to you is what turns panic into control. And as AI agents fire off commits and rebases you didn't write, the person who understands where git misleads is the one who untangles the mess. You were never bad at git. You were just never shown where it was built to trip you. Bookmark & Watch it today ↓

slash1s

138,043 次观看 • 26 天前

TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED 42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist. -> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you. Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening. Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster. Most people use 5% of git and call it a day. This is the other 95% nobody showed you. Bookmark it and Watch today ↓
42:40

TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED 42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist. -> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you. Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening. Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster. Most people use 5% of git and call it a day. This is the other 95% nobody showed you. Bookmark it and Watch today ↓

slash1s

104,813 次观看 • 24 天前

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 ↓
42:24

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

382,693 次观看 • 1 个月前

something I’ve wanted for a while: an AI that isn’t just a text box so I built it lets you create a 3D AI character on-chain that lives in your browser it can talk, remember you, show emotions, and use different skills. you can even mint it onchain, so it actually belongs to you it gets its own identity, history, and reputation that no one can take away most AI today can disappear if the app shuts down this one is permanent and yours the future is AI you can see, interact with, and actually own
1:23

something I’ve wanted for a while: an AI that isn’t just a text box so I built it lets you create a 3D AI character on-chain that lives in your browser it can talk, remember you, show emotions, and use different skills. you can even mint it onchain, so it actually belongs to you it gets its own identity, history, and reputation that no one can take away most AI today can disappear if the app shuts down this one is permanent and yours the future is AI you can see, interact with, and actually own

nich

256,465 次观看 • 2 个月前

Can one person change the culture of an organization? Yes. We all know that can definitely happen in a negative way. One person can shift the energy of a room, school, or an organization, to make it worse than what it was before. The opposite can be true as well. I saw individuals shift the culture of entire rooms in moments by bringing their energy and people fed off their enthusiasm, and the dynamic of the culture changed in moments. We often discuss culture like it’s someone else’s responsibility but culture is made up of people. And eventually that one person who can bring a positive light to an organization can diminish their own. No matter how optimistic, joyful and passionate a person can be, never assume they are “good.” Check in on people even when they seem like they don’t need it, because often they do. One person can move the culture ahead in a positive direction, but that individual might also need your energy to keep them going. Education is about elevation and whether you are positive or negative, it is contagious? Which one will you be?
1:25

Can one person change the culture of an organization? Yes. We all know that can definitely happen in a negative way. One person can shift the energy of a room, school, or an organization, to make it worse than what it was before. The opposite can be true as well. I saw individuals shift the culture of entire rooms in moments by bringing their energy and people fed off their enthusiasm, and the dynamic of the culture changed in moments. We often discuss culture like it’s someone else’s responsibility but culture is made up of people. And eventually that one person who can bring a positive light to an organization can diminish their own. No matter how optimistic, joyful and passionate a person can be, never assume they are “good.” Check in on people even when they seem like they don’t need it, because often they do. One person can move the culture ahead in a positive direction, but that individual might also need your energy to keep them going. Education is about elevation and whether you are positive or negative, it is contagious? Which one will you be?

George Couros

67,388 次观看 • 2 年前

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓
16:51

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓

slash1s

22,268 次观看 • 29 天前

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 ↓
36:09

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

191,595 次观看 • 1 个月前

The Hottest New AI Job: The Agent Maestro Jason: I think the job people are not seeing, but I'm seeing right now, is the person who creates, manages, and is the maestro of the agents. The person who can take the business process, explain it, and train the agent to do it. And there are certain people in business who are just really good at operations. You were one of them, Sacks, running companies. Fire up an agent, train them, and figure out how to manage them and increase their skills. It’s a great job, and it's not a developer. Sacks: With any new technology, there's always a huge change management aspect with enterprises because it's hard for them to adapt and change. And the people in the organization who can lead that change management are the ones who are going to create an amazing career opportunity for themselves.
0:46

The Hottest New AI Job: The Agent Maestro Jason: I think the job people are not seeing, but I'm seeing right now, is the person who creates, manages, and is the maestro of the agents. The person who can take the business process, explain it, and train the agent to do it. And there are certain people in business who are just really good at operations. You were one of them, Sacks, running companies. Fire up an agent, train them, and figure out how to manage them and increase their skills. It’s a great job, and it's not a developer. Sacks: With any new technology, there's always a huge change management aspect with enterprises because it's hard for them to adapt and change. And the people in the organization who can lead that change management are the ones who are going to create an amazing career opportunity for themselves.

The All-In Podcast

350,682 次观看 • 4 个月前

One of the best ways to win your time back with GitHub Copilot is to have it generate Git commit messages for you. Everyone has their own style - share yours with Copilot using Custom Instructions and save yourself a ton of time.
0:58

One of the best ways to win your time back with GitHub Copilot is to have it generate Git commit messages for you. Everyone has their own style - share yours with Copilot using Custom Instructions and save yourself a ton of time.

Visual Studio Code

66,210 次观看 • 1 年前

California has a right to protect its own people. From dirty air and dirty water. Now, Republicans in the Senate want to change that. And repeal California’s right to set its own policy, even as they eliminate the filibuster to do so. It is a precedent they will come to regret. That’s the thing about a slippery slope. You can be the one who starts down the slope but you don't get to be the one who decides where the ride stops.
1:18

California has a right to protect its own people. From dirty air and dirty water. Now, Republicans in the Senate want to change that. And repeal California’s right to set its own policy, even as they eliminate the filibuster to do so. It is a precedent they will come to regret. That’s the thing about a slippery slope. You can be the one who starts down the slope but you don't get to be the one who decides where the ride stops.

Adam Schiff

117,261 次观看 • 1 年前

HE MAKES MONEY IN REAL ESTATE WITHOUT BUYING, SELLING, OR EVEN SEEING A SINGLE HOUSE. HERE'S THE EXACT SETUP He never owns a property. He takes a single listing, turns it into a polished 30-second video, and sells that to the agent who posted it. Realtors need video for their feeds and almost none of them can make it. He sits in the middle and builds the whole thing once as a skill that runs on command Here is the exact process: 1. Pull the listing. Go to Zillow, open any listing, download the high-res images, and grab the property info. That is your raw material 2. Turn photos into video with Google Veo. Get a Google API key for Veo, the image-to-video model. It takes the listing photos and animates them into clean 30-second footage. This is the best one out right now 3. Add the voice with ElevenLabs. Get an ElevenLabs API key. Feed it the listing details and it returns a voiceover that sounds like a real human, not a robot. Lay it over the video with the text on screen 4. Send it with AgentMail. Get an AgentMail key so the system can send the finished email out on its own Then you wire it into one skill. Scrape the listing, send images to Veo, add the ElevenLabs voiceover and on-screen text, then send the email. Feed it each key one at a time and have it build each step Who you sell to: Pull realtors off Zillow and Realtor com whose listings have flat photos and zero video. That gap is your pitch. Send a free sample made from their own listing first, then charge a monthly rate for ongoing clips. One agent with ten listings is a recurring client, fully online Bookmark this
2:06

HE MAKES MONEY IN REAL ESTATE WITHOUT BUYING, SELLING, OR EVEN SEEING A SINGLE HOUSE. HERE'S THE EXACT SETUP He never owns a property. He takes a single listing, turns it into a polished 30-second video, and sells that to the agent who posted it. Realtors need video for their feeds and almost none of them can make it. He sits in the middle and builds the whole thing once as a skill that runs on command Here is the exact process: 1. Pull the listing. Go to Zillow, open any listing, download the high-res images, and grab the property info. That is your raw material 2. Turn photos into video with Google Veo. Get a Google API key for Veo, the image-to-video model. It takes the listing photos and animates them into clean 30-second footage. This is the best one out right now 3. Add the voice with ElevenLabs. Get an ElevenLabs API key. Feed it the listing details and it returns a voiceover that sounds like a real human, not a robot. Lay it over the video with the text on screen 4. Send it with AgentMail. Get an AgentMail key so the system can send the finished email out on its own Then you wire it into one skill. Scrape the listing, send images to Veo, add the ElevenLabs voiceover and on-screen text, then send the email. Feed it each key one at a time and have it build each step Who you sell to: Pull realtors off Zillow and Realtor com whose listings have flat photos and zero video. That gap is your pitch. Send a free sample made from their own listing first, then charge a monthly rate for ongoing clips. One agent with ten listings is a recurring client, fully online Bookmark this

Yarchi

106,174 次观看 • 1 个月前

The question we get the most with 8090 Enterprise engagements. Who maintains it and what happens when the software needs to change? Most custom software is built once and patched forever. Every change request becomes a six-week negotiation with a vendor who can no longer explain their own code. 8090 Enterprise inverts that. We design, build, host, AND maintain. Software Factory powers our delivery and is built for the second year of changes, the third year, and the tenth. Reach out to us about what system you want to replace: sales@8090.inc
0:40

The question we get the most with 8090 Enterprise engagements. Who maintains it and what happens when the software needs to change? Most custom software is built once and patched forever. Every change request becomes a six-week negotiation with a vendor who can no longer explain their own code. 8090 Enterprise inverts that. We design, build, host, AND maintain. Software Factory powers our delivery and is built for the second year of changes, the third year, and the tenth. Reach out to us about what system you want to replace: [email protected]

8090

120,538 次观看 • 1 个月前

The single best way to break into the Hedge Fund industry — and most people still won't do it: Derek Pilecki, 18-year track record, 21%+ annualized in financials, entire net worth in his own fund. "Since we have the internet, there's a way to break into the industry that didn't exist in the nineties." "You can write up stock ideas. You can research how to write up a stock idea. You can write up your own idea and post it to Seeking Alpha or create your own blog, post it to Twitter." "If you do that 10 times, you'll have a following." "There'll be professional money managers who will read your blog because you wrote up 10 small cap stocks and they own one or two of them." "They read your idea on this bank. They agreed with you. Now they wanna see what other banks you like." "You can find a job that way by just writing up stock ideas and posting them to the internet." "You can break into this industry if you're willing to do that work on your own and put yourself out there." You can just write up 10 stock ideas.
1:29

The single best way to break into the Hedge Fund industry — and most people still won't do it: Derek Pilecki, 18-year track record, 21%+ annualized in financials, entire net worth in his own fund. "Since we have the internet, there's a way to break into the industry that didn't exist in the nineties." "You can write up stock ideas. You can research how to write up a stock idea. You can write up your own idea and post it to Seeking Alpha or create your own blog, post it to Twitter." "If you do that 10 times, you'll have a following." "There'll be professional money managers who will read your blog because you wrote up 10 small cap stocks and they own one or two of them." "They read your idea on this bank. They agreed with you. Now they wanna see what other banks you like." "You can find a job that way by just writing up stock ideas and posting them to the internet." "You can break into this industry if you're willing to do that work on your own and put yourself out there." You can just write up 10 stock ideas.

Ethan Kho

200,481 次观看 • 3 个月前