Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

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 ↓show more

slash1s

10,042 subscribers

105,248 views • 2 months ago •via X (Twitter)

Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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 ↓

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

237,718 views • 2 months ago

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 ↓

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

458,408 views • 2 months ago

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 ↓

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 views • 2 months ago

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 ↓

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 views • 2 months ago

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 ↓

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,773 views • 2 months ago

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

384,696 views • 2 months ago

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.

slash1s

214,857 views • 2 months ago

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 don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓

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 don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓

slash1s

12,750 views • 2 months ago

A DEVELOPER TAUGHT GIT WITH A BOX OF CHILDREN'S TOYS AND ENGINEERS WITH TEN YEARS IN SAY IT'S THE FIRST TIME THE THING EVER ACTUALLY MADE SENSE 90 minutes, one table, a pile of Tinkertoys. No wall of jargon -- he builds a real Git repo out of plastic rods right in front of you. -> The moment he snaps the first pieces together, Git stops being scary command-line magic and becomes what it really is: a chain of tiny objects pointing at each other. Branches, merges, rebase, the staging area -- every concept that's ever burned you at 2am -- he rebuilds with toys until a four year old could follow. He calls Git a two-trick pony. After this you'll see exactly why. Memorizing commands was never the skill -> holding the graph in your head is. And with an AI agent now committing and rebasing on your machine all day, that mental model is the only thing between you and a history you can't read. Scroll the comments and you'll see the same thing over and over: this is the talk that finally made Git click and made people the one their whole team comes to when it breaks. Bookmark & watch it today. It's the 1.5 hours that pays you back for the rest of your career ↓

A DEVELOPER TAUGHT GIT WITH A BOX OF CHILDREN'S TOYS AND ENGINEERS WITH TEN YEARS IN SAY IT'S THE FIRST TIME THE THING EVER ACTUALLY MADE SENSE 90 minutes, one table, a pile of Tinkertoys. No wall of jargon -- he builds a real Git repo out of plastic rods right in front of you. -> The moment he snaps the first pieces together, Git stops being scary command-line magic and becomes what it really is: a chain of tiny objects pointing at each other. Branches, merges, rebase, the staging area -- every concept that's ever burned you at 2am -- he rebuilds with toys until a four year old could follow. He calls Git a two-trick pony. After this you'll see exactly why. Memorizing commands was never the skill -> holding the graph in your head is. And with an AI agent now committing and rebasing on your machine all day, that mental model is the only thing between you and a history you can't read. Scroll the comments and you'll see the same thing over and over: this is the talk that finally made Git click and made people the one their whole team comes to when it breaks. Bookmark & watch it today. It's the 1.5 hours that pays you back for the rest of your career ↓

slash1s

227,323 views • 2 months ago

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 views • 1 month ago

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.

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

252,255 views • 3 months ago

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 ↓

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 views • 2 months ago

THE CO-FOUNDER OF GITHUB GAVE A 46-MINUTE TALK ON GIT BECAUSE ENGINEERS WITH 10 YEARS IN HAVE NEVER SEEN HALF OF WHAT IT DOES This is Scott Chacon. He wrote Pro Git -- the book most devs secretly learned Git from and he co-founded GitHub. So when he says you're missing things, you're missing things. About ten minutes in it clicks: half the "git disasters" you've ever fixed by deleting the folder and re-cloning had a one-line solution sitting in the tool the whole time. Git ships new code almost every day -> roughly nine commits a day for over a decade. Most of us stopped learning it the second we memorized add, commit, push. Knowing Git isn't a senior-dev flex anymore -> it's the floor. The agent writes the code now. Your real job is reading, branching, and untangling the history it leaves behind. The day an AI agent force-pushes over your main branch, these 46 minutes are the difference between a quiet fix and a very loud apology. Save it now. You'll reach for it sooner than you'd like ↓

THE CO-FOUNDER OF GITHUB GAVE A 46-MINUTE TALK ON GIT BECAUSE ENGINEERS WITH 10 YEARS IN HAVE NEVER SEEN HALF OF WHAT IT DOES This is Scott Chacon. He wrote Pro Git -- the book most devs secretly learned Git from and he co-founded GitHub. So when he says you're missing things, you're missing things. About ten minutes in it clicks: half the "git disasters" you've ever fixed by deleting the folder and re-cloning had a one-line solution sitting in the tool the whole time. Git ships new code almost every day -> roughly nine commits a day for over a decade. Most of us stopped learning it the second we memorized add, commit, push. Knowing Git isn't a senior-dev flex anymore -> it's the floor. The agent writes the code now. Your real job is reading, branching, and untangling the history it leaves behind. The day an AI agent force-pushes over your main branch, these 46 minutes are the difference between a quiet fix and a very loud apology. Save it now. You'll reach for it sooner than you'd like ↓

slash1s

28,052 views • 2 months ago

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anthropic engineers finally showed how they actually use Claude Code internally 31 minutes of internal workflow that most Claude users will never see on their own here's what they cover: > how to set up project context files the right way > custom commands that save hours of repeated work > hooks that make Claude behave exactly how you need > subagents and how to actually spec them properly "your agent isn't the problem, your spec is" the people who understand how Claude Code actually works inside Anthropic are shipping things everyone else thinks requires a whole team that's exactly why I put together a breakdown of Claude features most people have never discovered you can find it below

Anatoli Kopadze

311,157 views • 2 months ago

Q : what do you think is the most difficult challenge you have faced this year that has made you stronger after a long time? #CHANYEOL : "wouldn't it be my 2nd album and my japan debut album? i prepared 12 songs at the same period of time, but to be honest, i don't consider it a difficult challenge because i really had fun working on them.. ah!! i do have one! a challenge i faced this year that made me stronger.. for me, it's git it up! git it up! was it february? ah, january! at the start of january. suho hyung and i did the git it up stage together at smtown. i think it was really a difficult challenge because we never had the chance to perform as EXO, just the two of us. i really had a lot of worries. but our performance was given so much love, many people liked it. it made me feel really good and gave me the motivation to keep on showing even more different sides of me in the future!"

Q : what do you think is the most difficult challenge you have faced this year that has made you stronger after a long time? #CHANYEOL : "wouldn't it be my 2nd album and my japan debut album? i prepared 12 songs at the same period of time, but to be honest, i don't consider it a difficult challenge because i really had fun working on them.. ah!! i do have one! a challenge i faced this year that made me stronger.. for me, it's git it up! git it up! was it february? ah, january! at the start of january. suho hyung and i did the git it up stage together at smtown. i think it was really a difficult challenge because we never had the chance to perform as EXO, just the two of us. i really had a lot of worries. but our performance was given so much love, many people liked it. it made me feel really good and gave me the motivation to keep on showing even more different sides of me in the future!"

NLNL 🍒🤟

34,603 views • 8 months ago

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 ↓

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

269,515 views • 2 months ago

Peter Jackson talks about AI in Hollywood. Calls it “a tool” like stop-motion or CGI before and what ultimately matters is “imagination, originality” of whoever uses the tool: “I think AI — used in the right way — is a tool like any other tool. [The original] King Kong…was stop-motion and done by a person moving a rubber creature. Why shouldn't somebody on a computer using AI software be able to create their own imagery? They should. It's a tool. It's no different from many other tools that have existed over the years. But the other side of it is that it's always going to come down to the imagination and originality of the person feeding the instructions into the AI program. It's not that you're going to type in an instruction and it's going to generate your shot, and that's that. The question is: is it actually interesting? Is it funny? Is it imaginative? And are you going to stitch it together to make a narrative, a story? Some people will make really great films that way. Some people will do exactly the same process and their film will be crap, just like in the normal film industry. Whether it's AI or anything else, it comes down to whether the person behind it — or the people behind it — have originality, imagination, and an ability to entertain people.”

Peter Jackson talks about AI in Hollywood. Calls it “a tool” like stop-motion or CGI before and what ultimately matters is “imagination, originality” of whoever uses the tool: “I think AI — used in the right way — is a tool like any other tool. [The original] King Kong…was stop-motion and done by a person moving a rubber creature. Why shouldn't somebody on a computer using AI software be able to create their own imagery? They should. It's a tool. It's no different from many other tools that have existed over the years. But the other side of it is that it's always going to come down to the imagination and originality of the person feeding the instructions into the AI program. It's not that you're going to type in an instruction and it's going to generate your shot, and that's that. The question is: is it actually interesting? Is it funny? Is it imaginative? And are you going to stitch it together to make a narrative, a story? Some people will make really great films that way. Some people will do exactly the same process and their film will be crap, just like in the normal film industry. Whether it's AI or anything else, it comes down to whether the person behind it — or the people behind it — have originality, imagination, and an ability to entertain people.”

Bearly AI

43,816 views • 3 months ago

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

433,431 views • 2 months ago

HARVARD HAS A FULL 53-MIN GIT LECTURE FROM DAVID MALAN BECAUSE 90% OF NEW DEVELOPERS STILL DON'T KNOW WHAT A COMMIT ACTUALLY IS 53 minutes of no-nonsense version control from the instructor whose course became the largest class in Harvard history. -> The moment you watch it, you realize why "I'll just push to main" is the fastest way to get fired in your first month. Every junior engineer in 2026 is expected to handle Git on day one - no excuses, no Stack Overflow, no AI hand-holding. Git isn't a "senior dev thing" anymore -> it's the literacy test for being in the room. The agent can ship the feature in 5 minutes. Recovering the repo it broke takes 5 hours - and only if you actually understand what happened. Don't forget to bookmark it.

HARVARD HAS A FULL 53-MIN GIT LECTURE FROM DAVID MALAN BECAUSE 90% OF NEW DEVELOPERS STILL DON'T KNOW WHAT A COMMIT ACTUALLY IS 53 minutes of no-nonsense version control from the instructor whose course became the largest class in Harvard history. -> The moment you watch it, you realize why "I'll just push to main" is the fastest way to get fired in your first month. Every junior engineer in 2026 is expected to handle Git on day one - no excuses, no Stack Overflow, no AI hand-holding. Git isn't a "senior dev thing" anymore -> it's the literacy test for being in the room. The agent can ship the feature in 5 minutes. Recovering the repo it broke takes 5 hours - and only if you actually understand what happened. Don't forget to bookmark it.

slash1s

253,313 views • 2 months ago

Steve Jobs on why everything around you was made by people no smarter than you: "When you grow up, you tend to get told that the world is the way it is and your life is just to live your life inside the world. Try not to bash into the walls too much, have a nice family life, have fun, save a little money. But that's a very limited life." Steve believed most people live with a fundamental misconception. As he puts it: "Life can be much broader once you discover one simple fact. And that is—everything around you that you call life was made up by people that were no smarter than you." He continues: "And you can change it. You can influence it. You can build your own things that other people can use. And the minute that you understand that you can poke life and actually something will pop out the other side—that you can change it, you can mold it." On what matters most: "Maybe the most important thing is to shake off this erroneous notion that life is there and you're just going to live in it versus embrace it, change it, improve it, make your mark upon it. I think that's very important." His perspective on why you should change things: "However you learn that, once you learn it, you'll want to change life and make it better because it's kind of messed up in a lot of ways." The shift: "Once you learn that, you'll never be the same again."

Steve Jobs on why everything around you was made by people no smarter than you: "When you grow up, you tend to get told that the world is the way it is and your life is just to live your life inside the world. Try not to bash into the walls too much, have a nice family life, have fun, save a little money. But that's a very limited life." Steve believed most people live with a fundamental misconception. As he puts it: "Life can be much broader once you discover one simple fact. And that is—everything around you that you call life was made up by people that were no smarter than you." He continues: "And you can change it. You can influence it. You can build your own things that other people can use. And the minute that you understand that you can poke life and actually something will pop out the other side—that you can change it, you can mold it." On what matters most: "Maybe the most important thing is to shake off this erroneous notion that life is there and you're just going to live in it versus embrace it, change it, improve it, make your mark upon it. I think that's very important." His perspective on why you should change things: "However you learn that, once you learn it, you'll want to change life and make it better because it's kind of messed up in a lot of ways." The shift: "Once you learn that, you'll never be the same again."

Jaynit

48,518 views • 7 months ago