Загрузка видео...

Не удалось загрузить видео

На главную

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

sahnlam's profile picture

Sahn Lam

48,880 subscribers

65,160 просмотров • 2 лет назад •via X (Twitter)

Новости и политикаНаука и технологииОбразование
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 5

Фото профиля deepPurple
deepPurple2 лет назад

I tried git rebase and end up with unresolved merges (shared project) which doesn’t let me checkout to feature branch with some weird messages like currently rebasing cannot checkout. What am I doing wrong 😑

Фото профиля Abdellah
Abdellah2 лет назад

I contributed to one popular library and the maintainer asked me to do a rebase. It wasn't easy to do because this is a feature of git I have never used it. So, he finally did the rebase for me. This is beneficial content. Please where can more of it be found?

Фото профиля Deisbel (Sr. Software Developer)
Deisbel (Sr. Software Developer)2 лет назад

Good details. Thank you for sharing them. One thing, In 20+ years I have never needed to do a Rebase. I wonder how many of you out there have done anything different of a git merge?

Фото профиля Who Am I
Who Am I2 лет назад

+

Фото профиля Python Space
Python Space2 лет назад

Very well explained with great visuals. 🙏

Похожие видео

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

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

slash1s

236,545 просмотров • 1 месяц назад

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

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

slash1s

37,693 просмотров • 1 месяц назад

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

457,083 просмотров • 1 месяц назад

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

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

slash1s

251,766 просмотров • 1 месяц назад

You don't need to memorize a dozen Git commands on day one. Start with the visual tools in VS Code, learn what commits and branches actually do, and build from there. That's exactly what we're covering in our latest GitHub for Beginners episode.
0:39

You don't need to memorize a dozen Git commands on day one. Start with the visual tools in VS Code, learn what commits and branches actually do, and build from there. That's exactly what we're covering in our latest GitHub for Beginners episode.

GitHub

24,544 просмотров • 1 месяц назад

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

27,973 просмотров • 1 месяц назад

There are times when delay is the most dangerous form of decision. That is why I am proposing a Competitiveness Handshake today. The Council, the Commission and the Parliament must all commit to one simple principle: no new net burden on European businesses. We all need to commit to making the EU work better for business.
0:40

There are times when delay is the most dangerous form of decision. That is why I am proposing a Competitiveness Handshake today. The Council, the Commission and the Parliament must all commit to one simple principle: no new net burden on European businesses. We all need to commit to making the EU work better for business.

Ebba Busch

42,931 просмотров • 4 месяцев назад

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 просмотров • 1 месяц назад

💧SCALLOP FEATURE - veSCA Merge & Split We are thrilled to introduce Scallop's latest feature, veSCA Merge and Split! This new feature provides Scallopers with the option to merge or split their different veSCA keys seamlessly, based on different needs and use cases! With this new feature update, Scallopers can perform the following actions: - Merge / Split veSCA - Manage multiple veSCA keys - Switching veSCA across multiple obligations With the ability to be split or merged into any size, veSCA is now as dynamic as a typical coin asset! 🎁Loyalty Program BONUS Airdrop Scallopers who claim and staked their SCA rewards in our recent loyalty program will receive a BONUS airdrop of 500,000 veSCA! Eligible Criteria: Hold at least 2,500 veSCA The bonus airdrop will be distributed in veSCA keys, with maximum lock duration of 4 years. Eligible Scallopers can claim their veSCA reward and choose to merge their new veSCA with their existing veSCA key! More Details Here:
0:31

💧SCALLOP FEATURE - veSCA Merge & Split We are thrilled to introduce Scallop's latest feature, veSCA Merge and Split! This new feature provides Scallopers with the option to merge or split their different veSCA keys seamlessly, based on different needs and use cases! With this new feature update, Scallopers can perform the following actions: - Merge / Split veSCA - Manage multiple veSCA keys - Switching veSCA across multiple obligations With the ability to be split or merged into any size, veSCA is now as dynamic as a typical coin asset! 🎁Loyalty Program BONUS Airdrop Scallopers who claim and staked their SCA rewards in our recent loyalty program will receive a BONUS airdrop of 500,000 veSCA! Eligible Criteria: Hold at least 2,500 veSCA The bonus airdrop will be distributed in veSCA keys, with maximum lock duration of 4 years. Eligible Scallopers can claim their veSCA reward and choose to merge their new veSCA with their existing veSCA key! More Details Here:

Scallop

19,111 просмотров • 1 год назад

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 ↓
1:39:13

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 просмотров • 1 месяц назад

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,248 просмотров • 1 месяц назад

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,688 просмотров • 1 месяц назад

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.
1:09:56

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

slash1s

214,079 просмотров • 1 месяц назад

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:
2:44

Maximizing your token throughput is one of the biggest productivity unlocks in Claude Code. So here's my guide to use multiple Claude Codes at the same time, effectively: - Run multiple Claude Code sessions at the same time, each on a different feature (Ghostty is great for this) - Use Claude Code's built in git worktrees to keep each instance isolated on its own branch (-w or --worktree flag) - Let Claude handle creating PRs or merging the worktree branches when you're done - Use the Claude Code Desktop app as your multi-agent control center Full guide below:

Avthar

10,723 просмотров • 3 месяцев назад

NEW: Vice President Vance condemns religious violence, calling it "one of the most anti-Christian things and anti-American things that you could do." "A fundamental principle of all the great faiths is we are all children of God. And because of that, we are endowed by certain rights that are unique to our status as human beings." "You violate those rights, most importantly, when you commit violence against another person, you can violate them in other ways as well, but the most profound way to violate the fundamental right of human dignity is to commit violence."
1:12

NEW: Vice President Vance condemns religious violence, calling it "one of the most anti-Christian things and anti-American things that you could do." "A fundamental principle of all the great faiths is we are all children of God. And because of that, we are endowed by certain rights that are unique to our status as human beings." "You violate those rights, most importantly, when you commit violence against another person, you can violate them in other ways as well, but the most profound way to violate the fundamental right of human dignity is to commit violence."

Fox News

49,380 просмотров • 2 месяцев назад

BANNON: God has chosen you to live in a time when the singularity is going to happen. You are gonna get weighed and measured, and if you stand up, if you commit tonight, if you think about this and you commit and I mean all in like you have through the dark days ahead and put sometimes our differences aside and say we gotta unify and back this guy. He's the one shot we have. We're gonna be victorious.
2:49

BANNON: God has chosen you to live in a time when the singularity is going to happen. You are gonna get weighed and measured, and if you stand up, if you commit tonight, if you think about this and you commit and I mean all in like you have through the dark days ahead and put sometimes our differences aside and say we gotta unify and back this guy. He's the one shot we have. We're gonna be victorious.

Bannon’s WarRoom

112,949 просмотров • 1 год назад

Simple Video about Vibe Coding a Game and Launching it on BaseApp in 10 Minutes 🟦 >Zero cost (Free) >No coding knowledge needed >You may become eligible for Base builder rewards >There are high chances of getting $BASE rewards in the future 🪂 Required links: >Base Dashboard: >Anti Gravity: >Vercel: To push the latest updates from a PowerShell terminal, use this command sequence: 👇 git add .; git commit -m "update"; git push Voice: ElevenLabs Cc :Base App Base Posting 🔖Bookmark this and don’t fade on Base
8:30

Simple Video about Vibe Coding a Game and Launching it on BaseApp in 10 Minutes 🟦 >Zero cost (Free) >No coding knowledge needed >You may become eligible for Base builder rewards >There are high chances of getting $BASE rewards in the future 🪂 Required links: >Base Dashboard: >Anti Gravity: >Vercel: To push the latest updates from a PowerShell terminal, use this command sequence: 👇 git add .; git commit -m "update"; git push Voice: ElevenLabs Cc :Base App Base Posting 🔖Bookmark this and don’t fade on Base

𝐙 𝐀 𝐗 🫧

55,773 просмотров • 3 месяцев назад

🚨 ENDORSEMENT 🚨 This morning, Fox & Friends weekend panel unanimously endorsed the Defend the Guard Act. H.B. 229, which passed the New Hampshire House of Representatives on Thursday, would prohibit the deployment of the state’s National Guard into overseas combat without a declaration of war from Congress. Pete Hegseth, a National Guardsman and veteran of both Iraq and Afghanistan, said “New Hampshire is simply pointing out that it’s supposed to be Congress that declares war. It has become an executive branch function, and as a result unless the Congress declares war, New Hampshire doesn’t have to send troops for foreign wars. To me it makes a lot of sense. I spent most of my career as a National Guardsman, deployed multiple times with the National Guard to foreign wars. We got used to the idea that state National Guard are part of expeditionary forces, which is not traditionally the use of a National Guard. And so this is New Hampshire saying we don’t trust how the federal government is going to use our troops, so we’re willing to commit them when the American people, through their elected branch in Congress, commits those troops to a foreign war, then you can. I love this idea. I’m sure the National Guard Bureau is [grumbles]. I love states exerting their influence through a system of federalism, and the idea of protecting the prerogative of—why are we sending some young guy from New Hampshire to the eastern province of Afghanistan when you have a northern border problem, or floods that happen in New Hampshire and they’re not there to provide support for that? It’s an interesting development, it’ll be interesting to see if other legislatures do this and how the military reacts to it.” Former White House Press Secretary Kayleigh McEnany asked “But why are states having to tell the federal government [to] abide by the letter of the Constitution? I love it as well, but it’s an unfortunate state of affairs when the states are having to say abide by the text.” Will Cain previously endorsed our bill when he interviewed our Chairman Dan McKnight while guest hosting Tucker Carlson Tonight.
2:14

🚨 ENDORSEMENT 🚨 This morning, Fox & Friends weekend panel unanimously endorsed the Defend the Guard Act. H.B. 229, which passed the New Hampshire House of Representatives on Thursday, would prohibit the deployment of the state’s National Guard into overseas combat without a declaration of war from Congress. Pete Hegseth, a National Guardsman and veteran of both Iraq and Afghanistan, said “New Hampshire is simply pointing out that it’s supposed to be Congress that declares war. It has become an executive branch function, and as a result unless the Congress declares war, New Hampshire doesn’t have to send troops for foreign wars. To me it makes a lot of sense. I spent most of my career as a National Guardsman, deployed multiple times with the National Guard to foreign wars. We got used to the idea that state National Guard are part of expeditionary forces, which is not traditionally the use of a National Guard. And so this is New Hampshire saying we don’t trust how the federal government is going to use our troops, so we’re willing to commit them when the American people, through their elected branch in Congress, commits those troops to a foreign war, then you can. I love this idea. I’m sure the National Guard Bureau is [grumbles]. I love states exerting their influence through a system of federalism, and the idea of protecting the prerogative of—why are we sending some young guy from New Hampshire to the eastern province of Afghanistan when you have a northern border problem, or floods that happen in New Hampshire and they’re not there to provide support for that? It’s an interesting development, it’ll be interesting to see if other legislatures do this and how the military reacts to it.” Former White House Press Secretary Kayleigh McEnany asked “But why are states having to tell the federal government [to] abide by the letter of the Constitution? I love it as well, but it’s an unfortunate state of affairs when the states are having to say abide by the text.” Will Cain previously endorsed our bill when he interviewed our Chairman Dan McKnight while guest hosting Tucker Carlson Tonight.

Bring Our Troops Home

159,693 просмотров • 2 лет назад

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 просмотров • 1 месяц назад

🚨NEW EPISODE🚨 🇮🇷Revolution in Iran: Death in the Desert🇮🇷 In the final part of our series on the Iranian Revolution, Tom and Dominic discuss: 🏜️Why did everything go wrong at ‘Desert One’? 🇺🇸What is the most American name in history? 🗳️Did Reagan commit treason to avoid a ‘October Surprise’?
0:56

🚨NEW EPISODE🚨 🇮🇷Revolution in Iran: Death in the Desert🇮🇷 In the final part of our series on the Iranian Revolution, Tom and Dominic discuss: 🏜️Why did everything go wrong at ‘Desert One’? 🇺🇸What is the most American name in history? 🗳️Did Reagan commit treason to avoid a ‘October Surprise’?

The Rest Is History

10,412 просмотров • 5 месяцев назад