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.

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

slash1s

10,067 subscribers

214,079 Aufrufe • vor 1 Monat •via X (Twitter)

Bildung Wissenschaft & Technologie

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

251,766 Aufrufe • vor 1 Monat

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 Aufrufe • vor 1 Monat

🚨 OpenAI 's own engineers just showed how to actually use OpenAI Codex properly. 60 minutes. free. built by the people who contribute to made it. watch the masterclass. bookmark it. worth more than every $900 coding course you almost bought. you’ve been using Codex like a simple coding tool… while it’s actually a full software engineering system. watch this, it could the best 62 minutes of your life:

🚨 OpenAI 's own engineers just showed how to actually use OpenAI Codex properly. 60 minutes. free. built by the people who contribute to made it. watch the masterclass. bookmark it. worth more than every $900 coding course you almost bought. you’ve been using Codex like a simple coding tool… while it’s actually a full software engineering system. watch this, it could the best 62 minutes of your life:

ZARA

296,432 Aufrufe • vor 2 Monaten

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 ↓

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

105,248 Aufrufe • vor 1 Monat

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 Aufrufe • vor 1 Monat

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

457,083 Aufrufe • vor 1 Monat

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 Aufrufe • vor 1 Monat

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

236,545 Aufrufe • vor 1 Monat

"We don't get to control the length of our adversity. You get to control who you are in it. The fastest way to get from a season of adversity to a season of prosperity is to ... figure out where you need to work and get better and then it will turn at some point."

"We don't get to control the length of our adversity. You get to control who you are in it. The fastest way to get from a season of adversity to a season of prosperity is to ... figure out where you need to work and get better and then it will turn at some point."

The Winning Difference

52,686 Aufrufe • vor 5 Monaten

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

27,973 Aufrufe • vor 1 Monat

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,693 Aufrufe • vor 1 Monat

Karpathy didn't make a course. He made THE course. 3 hours. Free. Tokenization. Attention. Hallucinations. Tool use. RLHF. DeepSeek. AlphaGo. Every behavior you've ever wondered about in an LLM - where it comes from, why it exists, how it was engineered. The gap between engineers who understand this and engineers who don't isn't technical depth. It's the ability to conceive of entirely different things.

Karpathy didn't make a course. He made THE course. 3 hours. Free. Tokenization. Attention. Hallucinations. Tool use. RLHF. DeepSeek. AlphaGo. Every behavior you've ever wondered about in an LLM - where it comes from, why it exists, how it was engineered. The gap between engineers who understand this and engineers who don't isn't technical depth. It's the ability to conceive of entirely different things.

Rahul

630,831 Aufrufe • vor 2 Monaten

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,688 Aufrufe • vor 1 Monat

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

383,642 Aufrufe • vor 1 Monat

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

226,935 Aufrufe • vor 1 Monat

Anthropic pays $750,000 a year for engineers who can build LLMs from scratch. Not prompt engineers. Not fine-tuners. Not RAG specialists. Engineers who understand the architecture well enough to build the thing from zero. Stanford just put a 2-hour lecture on exactly that on the internet for free. Scaling laws. Data collection. Architecture design. Post-training alignment. The theoretical foundation behind every model you use daily taught by the people who research it at one of the best CS programs on earth. Free. From Stanford. Two hours. The engineers earning $750,000 at Anthropic understand everything in this lecture. Most people using AI every day understand none of it. Watch it tonight. Full implementation guide in the article below.

Anthropic pays $750,000 a year for engineers who can build LLMs from scratch. Not prompt engineers. Not fine-tuners. Not RAG specialists. Engineers who understand the architecture well enough to build the thing from zero. Stanford just put a 2-hour lecture on exactly that on the internet for free. Scaling laws. Data collection. Architecture design. Post-training alignment. The theoretical foundation behind every model you use daily taught by the people who research it at one of the best CS programs on earth. Free. From Stanford. Two hours. The engineers earning $750,000 at Anthropic understand everything in this lecture. Most people using AI every day understand none of it. Watch it tonight. Full implementation guide in the article below.

CyrilXBT

36,692 Aufrufe • vor 1 Monat

Highly recommend giving Odd Taxi a watch if you need a new anime. It's only 13 episodes so it's not a big commitment. It's like a Quentin Tarantino movie in a series. Don't let the art style fool you, it's very complex. It follows the life of a taxi driver (the walrus) named Odokawa who somehow finds himself involved in missing schoolgirl, the police, the yakuza, and many other interesting characters. All from the perspective of being just a simple driver. What's interesting is the entire plot to the series is fully laid out in the opening credits, but you'll never be able to figure it out without seeing it. It's a gem, give it a watch. Lots of twists and turns. You won't regret it.

Highly recommend giving Odd Taxi a watch if you need a new anime. It's only 13 episodes so it's not a big commitment. It's like a Quentin Tarantino movie in a series. Don't let the art style fool you, it's very complex. It follows the life of a taxi driver (the walrus) named Odokawa who somehow finds himself involved in missing schoolgirl, the police, the yakuza, and many other interesting characters. All from the perspective of being just a simple driver. What's interesting is the entire plot to the series is fully laid out in the opening credits, but you'll never be able to figure it out without seeing it. It's a gem, give it a watch. Lots of twists and turns. You won't regret it.

Autism Capital 🧩

47,680 Aufrufe • vor 1 Monat

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 1 Monat

THIS GUY JUST BUILT A DRONE THAT TRACKS TARGETS WITH A LASER USING CLAUDE > No robotics team > No engineering degree > No budget He used Claude Code to write the entire system in Python - a drone that locks onto a target, follows it with a laser and corrects its own aim automatically after every attempt. The AI gets more accurate the longer it runs because it learns from every single shot. He's still improving it and this is only the beginning. You have the same tool he used. The article below is about how to actually use it to its full potential.

THIS GUY JUST BUILT A DRONE THAT TRACKS TARGETS WITH A LASER USING CLAUDE > No robotics team > No engineering degree > No budget He used Claude Code to write the entire system in Python - a drone that locks onto a target, follows it with a laser and corrects its own aim automatically after every attempt. The AI gets more accurate the longer it runs because it learns from every single shot. He's still improving it and this is only the beginning. You have the same tool he used. The article below is about how to actually use it to its full potential.

Anatoli Kopadze

275,518 Aufrufe • vor 2 Monaten

Denzel Washington in 2016. Still the most accurate media roast ever. "If you don't read the newspaper, you're uninformed. If you do read it, you're misinformed. "What is the long-term effect of too much information? One of the effects is the need to be first, even if it's not true anymore" "We live in a society now where it's just first who cares? Get it out there. We don't care who it hurts. We don't care who we destroy. We don't care if it's true. Just say it, sell it. Anything you practice, you'll get good at, including bullsh*t."

Denzel Washington in 2016. Still the most accurate media roast ever. "If you don't read the newspaper, you're uninformed. If you do read it, you're misinformed. "What is the long-term effect of too much information? One of the effects is the need to be first, even if it's not true anymore" "We live in a society now where it's just first who cares? Get it out there. We don't care who it hurts. We don't care who we destroy. We don't care if it's true. Just say it, sell it. Anything you practice, you'll get good at, including bullsh*t."

Defiant Ghost

22,941 Aufrufe • vor 4 Monaten