Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

slash1sol's profile picture

slash1s

13,786 subscribers

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

EğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

40 Yorum

Xavi profil fotoğrafı
Xavi5 ay önce

If 99% use it wrong then something is wrong with the design

slash1s profil fotoğrafı
slash1s5 ay önce

maybe..

rikrdo profil fotoğrafı
rikrdo5 ay önce

The guy who built Git? The guy who built Git is Linus Torvalds.

slash1s profil fotoğrafı
slash1s5 ay önce

take a closer look🙏

cristal💎 profil fotoğrafı
cristal💎5 ay önce

subversion and cvs torn to pieces

slash1s profil fotoğrafı
slash1s5 ay önce

🤝

Max Fang (Lexe.app) profil fotoğrafı
Max Fang (Lexe.app)5 ay önce

This 🚨 URGENT IMPORTANT BREAKING HEADLINE STYLE 🚨!!! is so tiring man

slash1s profil fotoğrafı
slash1s5 ay önce

sorry bro

Marc Espie profil fotoğrafı
Marc Espie5 ay önce

You wouldn't have a decent quality video, would you ? that one makes my eyes bleed.

slash1s profil fotoğrafı
slash1s5 ay önce

sorry it’s from 2007 and have only this quality..

CaptainAmericaTex profil fotoğrafı
CaptainAmericaTex5 ay önce

The worst error is corporations going to settings, and enabling the optional feature "Pull Request review" before merge. In the original git, a PR is meant for _external_ parties contributions. Internal developers were meant to push and merge directly.

Steve Cox profil fotoğrafı
Steve Cox5 ay önce

Not everyone is building an open source operating system. The git was built to handle 1000s of developers contributing to a code base doing a very specific thing in one programming language.

cvxv666 profil fotoğrafı
cvxv6665 ay önce

that was very useful hour, thx

slash1s profil fotoğrafı
slash1s5 ay önce

u are welcome bro

sukru tikves profil fotoğrafı
sukru tikves5 ay önce

(I haven't watched the talk, tl;dr;) But I had used both Perforce and Git when I worked at Google. Which one was better? Mercurial ... by a wide mile I respect Linus, but sometimes a tool is not the best suited for every use case.

_fabianodigital_ profil fotoğrafı
_fabianodigital_5 ay önce

@carlosurda_77 I am fine with SVN, thanks

BoVodio Toad profil fotoğrafı
BoVodio Toad5 ay önce

Because fuck GIT.

Archive profil fotoğrafı
Archive5 ay önce

I'm canceling all my plans for today and going to watch this video thanks dude

shmidt profil fotoğrafı
shmidt5 ay önce

linus going on a 70 min rant about git is peak internet. pretty sure he was calling us all idiots the whole time

David Lypka profil fotoğrafı
David Lypka5 ay önce

Git does not save to a blockchain so it is not the Ultimate Source Control Tool and that was not the Ultimate Lecture. He does not seem to understand that the only reliable Control is to Zip the entire Project.

leopardracer profil fotoğrafı
leopardracer5 ay önce

thanks for sharing this, bookmarked 🙌🏽

Atenov int. profil fotoğrafı
Atenov int.5 ay önce

and now i see why my team struggles with merges

Orion profil fotoğrafı
Orion5 ay önce

@grok summarize the contents of the video

Justin Andrusk profil fotoğrafı
Justin Andrusk5 ay önce

This is the correct way to use it:

nap taker° 💚🙂🏴 profil fotoğrafı
nap taker° 💚🙂🏴5 ay önce

@NotADebacle

Dinh Chung profil fotoğrafı
Dinh Chung5 ay önce

Linus Torvaldsはすごいですね。彼が語ることは重要です。もし間違った使い方をしているなら、改善することが必要かもしれませんね。彼の講義を見ると学びがあると思います。あなたはGitをどのように使用していますか？

Tarrito.rocks profil fotoğrafı
Tarrito.rocks5 ay önce

"THE GUY WHO BUILT GIT GAVE ...."????? That guy it is not Linus Torvalds at all

StarShipX profil fotoğrafı
StarShipX5 ay önce

誰もがGitを誤って使用しているとしたら、それを正しく使用するべきだと考える人物がGoogleで完全な講義を行いました。 Linus Torvalds自らがLinuxとGitの両方をゼロから書いた人物です。

Gia huy profil fotoğrafı
Gia huy5 ay önce

Torvalds thật sự tuyệt vời! Git là hệ điều hành của codebase.

Logics profil fotoğrafı
Logics5 ay önce

bookmarked o7

Ridark profil fotoğrafı
Ridark5 ay önce

Incredibly useful material, added to favorites

Yamikishi profil fotoğrafı
Yamikishi5 ay önce

I rewatch this lecture once a year. The underlying philosophy of Git makes so much sense after you see this

sandybrige profil fotoğrafı
sandybrige5 ay önce

彼のフルレクチャーを見た後、Gitの重要性がより明確になった。

Harry Tandy profil fotoğrafı
Harry Tandy5 ay önce

Linus Torvalds never holds back on clear design principles

NMhao profil fotoğrafı
NMhao5 ay önce

彼はそれを説明するのに10分かからず、Googleのエンジニア達にそれを見せびらかしました。 Gitはもはや"あると便利なら"ではなく、あなたが触れたすべてのコードベースのオペレーティングシステムです。是非チェックしてみてください。

Insomnia profil fotoğrafı
Insomnia5 ay önce

100% worth to booked and listen again

zostaff profil fotoğrafı
zostaff5 ay önce

linus calling out google engineers on perforce is peak comedy

Bizzi profil fotoğrafı
Bizzi5 ay önce

So useful for devs I guess

Nekt0 profil fotoğrafı
Nekt05 ay önce

I'm amazed at how much useful information you're sharing

glück profil fotoğrafı
glück5 ay önce

Git нельзя использовать неправильно. Любой воркфлоу с ним.

Benzer Videolar

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

253,577 görüntüleme • 5 ay önce

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.
53:11

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 görüntüleme • 5 ay önce

🚨 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:
1:01:43

🚨 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

301,512 görüntüleme • 6 ay önce

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

105,823 görüntüleme • 5 ay önce

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 görüntüleme • 5 ay önce

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

460,475 görüntüleme • 5 ay önce

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 görüntüleme • 5 ay önce

Google engineer: "Delete your IDE, you don't need it anymore, in 2026 if you're still not building AI agents, it's crazy how behind you are. At Google, 85% of engineers are running agentic loops and graphs, that's how the engineering setup looks now." 25 minutes from a Google engineer with 30 years of experience, explaining where engineering is heading in 2026. This is something you can't skip if you don't want to be left behind. Watch it, then go further with the step-by-step guide below on how to build a system that improves itself.
24:23

Google engineer: "Delete your IDE, you don't need it anymore, in 2026 if you're still not building AI agents, it's crazy how behind you are. At Google, 85% of engineers are running agentic loops and graphs, that's how the engineering setup looks now." 25 minutes from a Google engineer with 30 years of experience, explaining where engineering is heading in 2026. This is something you can't skip if you don't want to be left behind. Watch it, then go further with the step-by-step guide below on how to build a system that improves itself.

Anatoli Kopadze

70,986 görüntüleme • 2 ay önce

Google engineer: "90% of engineers are still using LLMs like ChatGPT & Claude wrong. They run 1 agent, it fails, they say 'it's dumb' at Google, all senior engineers already running "loops" and "graphs" for their self-learning agentic systems" in a 18-minute session, a Google engineer explains how to build a self-learning agentic system from scratch watch today if you don't want to be left behind, then read the article below
18:04

Google engineer: "90% of engineers are still using LLMs like ChatGPT & Claude wrong. They run 1 agent, it fails, they say 'it's dumb' at Google, all senior engineers already running "loops" and "graphs" for their self-learning agentic systems" in a 18-minute session, a Google engineer explains how to build a self-learning agentic system from scratch watch today if you don't want to be left behind, then read the article below

Movez

22,337 görüntüleme • 2 ay önce

Head of Google AI at Stanford: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 40-minutes, reveal how one engineer can do a whole team’s work at Google, and what's coming for AI this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.
41:02

Head of Google AI at Stanford: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 40-minutes, reveal how one engineer can do a whole team’s work at Google, and what's coming for AI this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.

Codez

21,164 görüntüleme • 3 ay önce

Head of Google AI: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 50-minutes, he shows how one engineer can do a whole team’s work, how far this has gone at Google, and what’s next. this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.
56:58

Head of Google AI: "75% of our engineers are running dozens or hundreds of agents. The way you do it is Graph Engineering." in 50-minutes, he shows how one engineer can do a whole team’s work, how far this has gone at Google, and what’s next. this is something you can't skip if you don't want to be left behind. watch it, then read the full guide on graph engineering below.

Codez

76,425 görüntüleme • 3 ay önce

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

239,491 görüntüleme • 5 ay önce

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 ↓
46:04

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,178 görüntüleme • 5 ay önce

"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."
0:45

"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

53,009 görüntüleme • 8 ay önce

Google engineer: "delete your IDE, you don't need it anymore. in 2026 if you are still not building AI agents, it's crazy how bad you are At Google, 85% of engineers are running agentic "loops" and graphs, that's how the engineering setup will look" in a 25-minute session, a Google engineer with 30 years of experience reveals how AI engineering will look like in 2026 Worth more than 10 paid agentic courses Watch it today, then read how to run a self-improving agentic system in the article below
24:04

Google engineer: "delete your IDE, you don't need it anymore. in 2026 if you are still not building AI agents, it's crazy how bad you are At Google, 85% of engineers are running agentic "loops" and graphs, that's how the engineering setup will look" in a 25-minute session, a Google engineer with 30 years of experience reveals how AI engineering will look like in 2026 Worth more than 10 paid agentic courses Watch it today, then read how to run a self-improving agentic system in the article below

Movez

1,193,484 görüntüleme • 2 ay önce

Linus Torvalds remembers those first reactions to the Git interface. 👀 Here's why he did things differently when launching the version control system we know and love today. ▶️ Learn more about the early days of Git in our full interview. 🎙️ ⬇️
0:45

Linus Torvalds remembers those first reactions to the Git interface. 👀 Here's why he did things differently when launching the version control system we know and love today. ▶️ Learn more about the early days of Git in our full interview. 🎙️ ⬇️

GitHub

79,319 görüntüleme • 1 yıl önce

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,960 görüntüleme • 5 ay önce

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 ↓
55:43

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,797 görüntüleme • 5 ay önce

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

387,103 görüntüleme • 5 ay önce

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.
3:31:23

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

635,769 görüntüleme • 6 ay önce