正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

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

slash1s

14,023 subscribers

253,577 次观看 • 5 个月前 •via X (Twitter)

教育科学技术

Anya Rossi• Live Now

Private livecam show

42 条评论

David Ha 的头像

David Ha5 个月前

Also on their YouTube channel:

Gipp 🦅 的头像

Gipp 🦅5 个月前

The master class is really very cool

slash1s 的头像

slash1s5 个月前

fully agree

Ventry 的头像

Ventry5 个月前

thanks for the vid bro think this'll come in handy

slash1s 的头像

slash1s5 个月前

good

Ridark 的头像

Ridark5 个月前

an hour and 5 minutes of an interesting lecture

slash1s 的头像

slash1s5 个月前

yep

Allen Braden 的头像

Allen Braden5 个月前

Excellent course.

h100envy 的头像

h100envy5 个月前

"vibe-coders still don't know how to commit" both git and emotionally

justphil 的头像

justphil5 个月前

What? A 65 min class on git and github? This could have been an email... 😆

cvxv666 的头像

cvxv6665 个月前

tbh I was confused too when I made my first commit with Claude

slash1s 的头像

slash1s5 个月前

oh bro

kiosa 的头像

kiosa5 个月前

Actually, this repo is so useful, I used it last week on my project

slash1s 的头像

slash1s5 个月前

🤝

Bizzi 的头像

Bizzi5 个月前

Need to listen authorities from Harvard)

slash1s 的头像

slash1s5 个月前

100%

Jorg Brown 的头像

Jorg Brown5 个月前

The problem isn’t what you don’t know. The problem is git itself. Git puts everything in easy reach, regardless of how useless or destructive. If cars were designed like git, there would be seven pedals on the floor: brake, clutch, hood release, parking brake, gas pedal, passenger eject, and windshield wipers. And mistakenly ejected passengers would be a common problem, for which most people would blame bad drivers. It’s infuriating.

Terry Bui 的头像

Terry Bui5 个月前

プログラミングを学ぶ人にとって、GitとGitHubのマスタークラスは必須ですね。それを見た瞬間、開発者たちがなぜプロダクションブランチを壊しているのかが分かります。最近のテクノロジーカンパニーは、基本的なマージの衝突を処理できない候補者を除外しています。Gitはもはや「知っておくと便利」ではありません->それはコンプライアンスです。AIはコードを書けますが、問題はリポジトリを壊さずにマージする方法を知らないことです。お気に入りに入れるのを忘れないでください。

Fokki 的头像

Fokki5 个月前

ty as always for alpha

slash1s 的头像

slash1s5 个月前

🫡

leopardracer 的头像

leopardracer5 个月前

bookmarked

slash1s 的头像

slash1s5 个月前

ty

zostaff 的头像

zostaff5 个月前

cs50 git course slaps, but harvard didn't make it for vibe coders lol they just reposted it

고조 체인 的头像

고조 체인5 个月前

bro that 65 min vid gonna expose half the “senior devs” i know~~

vorty 的头像

vorty5 个月前

saved, watching all 65 minutes this week

Novice Adam 的头像

Novice Adam5 个月前

What I’m learning about Git Proficiency Basic/Junior (many vibe coders lack) Init repo, add/commit/push/pull Create/switch branches (main vs feature branches) Resolve simple merge conflicts Decent commit messages Clone + set up remotes Intermediate (what companies expect) Branching strategies (Git Flow, trunk-based) Atomic commits (no giant “WIP”) Comfy merge conflicts Intentional rebase vs merge (rebase -i to clean history) stash, cherry-pick, reset (soft/hard/mixed) .gitignore, hooks, basic CI/CD Effective PRs/MRs + reviews bisect to find when a bug was introduced Advanced/Senior+ Git internals (objects, refs, index, packfiles) Adv rebasing, reflog recovery, history rewriting Submodules or monorepo management Git hooks for enforcing standards Optimizing large repos, LFS, partial clones Designing team workflows & Git policies

EMOTION CRYPTO 的头像

EMOTION CRYPTO5 个月前

1 hours alpha

relic.avax 🔺 的头像

relic.avax 🔺5 个月前

Never once had a single issue lol

Rex 的头像

Rex5 个月前

So show of hands is out of favor now? Green smiley face 😂

Seven 的头像

Seven5 个月前

It’s not our fault that you made it so complicated that we feel retarded every time we go in there. it’s so poorly laid out and the user interface is just shit. It’s absolutely ridiculous for anyone on the spectrum.

Nucleus 的头像

Nucleus5 个月前

Very much appreciated 👊

slash1s 的头像

slash1s5 个月前

🤝

Deydara 的头像

Deydara5 个月前

A really great podcast

Dipanshu Kushwaha 的头像

Dipanshu Kushwaha5 个月前

Sounds like a game changer! Can’t wait to dive in and finally master those commits. Thanks for the heads up!

한류 & GG 的头像

한류 & GG5 个月前

merge conflicts > vibe coding

Chris Brisson 的头像

Chris Brisson5 个月前

It’s 7 years old but none the less I’m sure it’s good. Is there an updated version?

leakgambler 的头像

leakgambler5 个月前

"AI writes the code, u break the repo merging it" - which git operation do vibe-coders mess up most?

Ai Machete 的头像

Ai Machete5 个月前

Bookmarked. Exceptional info! Thank you!

kvro 的头像

kvro5 个月前

merge conflicts compliance now not nice-to-know

Parletto 的头像

Parletto5 个月前

solid foundation for anyone trying to level up

Jonatha Nfisher | Pumpkin.xyz DEX 的头像

Jonatha Nfisher | Pumpkin.xyz DEX5 个月前

But Harvard's masterclass ignores crypto-specific versioning for smart contracts.

Atenov int. 的头像

Atenov int.5 个月前

and now top devs are filtered by git skills not code quality

相关视频

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 次观看 • 5 个月前

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

215,473 次观看 • 5 个月前

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,797 次观看 • 4 个月前

Jane Street rejected this vibe-coder at $385K/year because he refused to use Claude Code 32-min of vibe coding RIGHT during an interview at a Tier 1 fund you watch the entire process: live coding, pressure questions, the moment they realize his stack doesn't match theirs every Tier-1 fund is now filtering candidates by tool stack. Claude Code is the new compliance Bookmark & Watch tonight

Jane Street rejected this vibe-coder at $385K/year because he refused to use Claude Code 32-min of vibe coding RIGHT during an interview at a Tier 1 fund you watch the entire process: live coding, pressure questions, the moment they realize his stack doesn't match theirs every Tier-1 fund is now filtering candidates by tool stack. Claude Code is the new compliance Bookmark & Watch tonight

Paone

3,543,533 次观看 • 5 个月前

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,823 次观看 • 4 个月前

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

239,491 次观看 • 4 个月前

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

460,446 次观看 • 4 个月前

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,960 次观看 • 4 个月前

Zach who built Cal AI and sold it for millions at 19 says: solving your own problem is the cheat code because product and marketing collapse into the same challenge: "If you're really solving your own problem, it really makes everything fall into place because you know exactly what you would want out of the product you're building. So it makes the app design very intuitive." "With the marketing, you know exactly who you're marketing to because it's marketing to yourself. And so you know exactly the pain points that you hit on." "If you don't know the idea to necessarily look for something that would actually help you. It's a great way to start."

Zach who built Cal AI and sold it for millions at 19 says: solving your own problem is the cheat code because product and marketing collapse into the same challenge: "If you're really solving your own problem, it really makes everything fall into place because you know exactly what you would want out of the product you're building. So it makes the app design very intuitive." "With the marketing, you know exactly who you're marketing to because it's marketing to yourself. And so you know exactly the pain points that you hit on." "If you don't know the idea to necessarily look for something that would actually help you. It's a great way to start."

Starter Story

18,892 次观看 • 1 个月前

Why does every woman want to imitate black people and h*mosexuals now? It's disgusting. "But I just can't do it anymore with the faces. I don't know what that is. I don't know what you call it. I don't know who... people are saying Black. It's a Black thing."

Sensitive content

Why does every woman want to imitate black people and h*mosexuals now? It's disgusting. "But I just can't do it anymore with the faces. I don't know what that is. I don't know what you call it. I don't know who... people are saying Black. It's a Black thing."

YoungGroypClips

35,383 次观看 • 21 天前

YoYo - New 'Git' for Vibe coders This open source extension allows me to do version control of AI generated codes in Cursor/Claude Code, So we can iterate different UI/UX flow much easier ----- It's interesting how basic things like Git can be rethink in the era of AI coding, Especially when we have 2~3 background agents working on the same code base simultaneously, We prob need new type of Git experience that allow agents to collab & resolve merge conflicts easily, We are just scratching the surface

YoYo - New 'Git' for Vibe coders This open source extension allows me to do version control of AI generated codes in Cursor/Claude Code, So we can iterate different UI/UX flow much easier ----- It's interesting how basic things like Git can be rethink in the era of AI coding, Especially when we have 2~3 background agents working on the same code base simultaneously, We prob need new type of Git experience that allow agents to collab & resolve merge conflicts easily, We are just scratching the surface

Jason Zhou

41,969 次观看 • 1 年前

Git Merge vs. Rebase vs. Squash Commit What are the differences and when should you use each? As I explain in more detail in the video, there are some key distinctions. Git Merge This creates a new commit in the target branch. The new commit ties the histories of both main and feature branches together. Git merge is non-destructive - it introduces a new commit without altering existing ones. Git Rebase Rebase transplants commits to the tip of another branch. It creates new commits for each one moved over. The benefit is linear history. But be cautious with shared branches to avoid confusing collaborators. Squash Commit Squashing condenses multiple commits into one, streamlining the commit history. Watch the video to see when to use merge vs rebase vs squash when incorporating changes between main and feature branches. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Git Merge vs. Rebase vs. Squash Commit What are the differences and when should you use each? As I explain in more detail in the video, there are some key distinctions. Git Merge This creates a new commit in the target branch. The new commit ties the histories of both main and feature branches together. Git merge is non-destructive - it introduces a new commit without altering existing ones. Git Rebase Rebase transplants commits to the tip of another branch. It creates new commits for each one moved over. The benefit is linear history. But be cautious with shared branches to avoid confusing collaborators. Squash Commit Squashing condenses multiple commits into one, streamlining the commit history. Watch the video to see when to use merge vs rebase vs squash when incorporating changes between main and feature branches. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Sahn Lam

65,234 次观看 • 2 年前

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 次观看 • 4 个月前

Q: Can you expand on your comment that nobody has any idea why Bondi is no longer the AG? It seems like it's a problem if you don't know what the president wants you to be doing better BLANCHE: That's an assumption baked into your question that I don't know is true

Q: Can you expand on your comment that nobody has any idea why Bondi is no longer the AG? It seems like it's a problem if you don't know what the president wants you to be doing better BLANCHE: That's an assumption baked into your question that I don't know is true

Aaron Rupar

112,497 次观看 • 6 个月前

"Ever wonder why... the school systems don't teach any real life skills anymore?" "Because the moment a man becomes self-reliant, the system loses control." "They don't want you to know how to survive without them. They want you dependent. They want you obedient. They want you to be reliant on the government. And so they teach kids how to comply, not how to think." "Self-reliance is dangerous to the people who crave power, because once you can feed yourself, once you can defend yourself, once you can think for yourself, they can't control you anymore." "That's why they vilify independence, because the system doesn't fear rebellion—it fears men who no longer need it." "The strongest rebellion left in the world is a man who refuses to depend on a system that's trying to enslave him." 🎯

"Ever wonder why... the school systems don't teach any real life skills anymore?" "Because the moment a man becomes self-reliant, the system loses control." "They don't want you to know how to survive without them. They want you dependent. They want you obedient. They want you to be reliant on the government. And so they teach kids how to comply, not how to think." "Self-reliance is dangerous to the people who crave power, because once you can feed yourself, once you can defend yourself, once you can think for yourself, they can't control you anymore." "That's why they vilify independence, because the system doesn't fear rebellion—it fears men who no longer need it." "The strongest rebellion left in the world is a man who refuses to depend on a system that's trying to enslave him." 🎯

Wide Awake Media

44,486 次观看 • 11 个月前

Stephen A. Smith says he will never be married because he couldn't be faithful and didn't know how to act Host: "If you know so much about marriage then why have you never been married?" Stephen: "Because I didn't know how to act" Host: "is it your fault?" Stephen: "Totally my fault and It's not anybody's fault but mine...I was on the road over 200 days out of the year. I'm not going to be faithful being on the road 200 days out of the year" "This is the part that men don't reveal that much but I will do it is that when you get older you don't need it anymore so you don't chase. That's entirely different from when it's handed to you on a silver platter. It doesn't mean you can't say no. It means it's harder"

Stephen A. Smith says he will never be married because he couldn't be faithful and didn't know how to act Host: "If you know so much about marriage then why have you never been married?" Stephen: "Because I didn't know how to act" Host: "is it your fault?" Stephen: "Totally my fault and It's not anybody's fault but mine...I was on the road over 200 days out of the year. I'm not going to be faithful being on the road 200 days out of the year" "This is the part that men don't reveal that much but I will do it is that when you get older you don't need it anymore so you don't chase. That's entirely different from when it's handed to you on a silver platter. It doesn't mean you can't say no. It means it's harder"

CreativeDude

847,913 次观看 • 3 个月前

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Claude Code creator: "100% of our pull requests at Anrtopic are run by Claude Code. 80–90% of code review too. The feature I’m using the most today is /loops. I’m not prompting Claude anymore - I’m building loops" in this interview he breaks down exactly how a system changes everything: - the memory and context features that turn Claude into a second brain - the knowledge architecture most users don't know Claude can build - the integration layer that connects Claude to your actual workflow - why typing one question at a time is the most expensive way to use Claude if you've been using Claude for months and still start every conversation from scratch with zero context, you don't have a Claude problem. you have a system problem instead of another show tonight, watch this make sure to bookmark it before it gets lost in your feed full guide in the article below

Khairallah AL-Awady

39,381 次观看 • 4 个月前

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

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

slash1s

386,950 次观看 • 4 个月前

JUST IN: 🇺🇸🇮🇷 Trump refuses to admit that Iran is fighting back without a problem. He started arguing with the reporter who asked him that “There are no signs that Iran is ready to stop fighting and what is the plan” President Trump: ‘How would you know? How would you know if there are no signs? Why? Why do you know something that I don’t know?’

JUST IN: 🇺🇸🇮🇷 Trump refuses to admit that Iran is fighting back without a problem. He started arguing with the reporter who asked him that “There are no signs that Iran is ready to stop fighting and what is the plan” President Trump: ‘How would you know? How would you know if there are no signs? Why? Why do you know something that I don’t know?’

Megatron

148,797 次观看 • 3 个月前