Loading video...

Video Failed to Load

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

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

slash1s

7,938 subscribers

224,970 views • 3 days ago •via X (Twitter)

Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

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

slash1s

221,442 views • 6 days ago

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

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

slash1s

376,043 views • 4 days ago

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

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

slash1s

27,380 views • 7 days ago

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

slash1s

186,904 views • 2 days ago

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,160 views • 2 years ago

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

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

slash1s

249,033 views • 17 days ago

Try this Git developer challenge: a bug appeared somewhere in the last 500 commits, and you have a test that detects it. What’s the shortest path to find the exact commit where it was introduced? Share your answer in the comments.

Try this Git developer challenge: a bug appeared somewhere in the last 500 commits, and you have a test that detects it. What’s the shortest path to find the exact commit where it was introduced? Share your answer in the comments.

Google for Developers

16,397 views • 1 month ago

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

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

slash1s

210,930 views • 12 days ago

Introducing `gut` - an AI agent for git 🤖🧑‍💻 This is a really neat CLI-based tool from Clelia Bertelli that lets you ask about and execute git commands through natural language! Describe what you want to do in English (e.g. a complex rebase), and it’ll let you review and auto-execute each command while explaining what it does. It’s a neat, minimal helper tool for anyone ramping up on version control tools like git + GitHub. Powered by LlamaIndex 🦙 workflows and Groq Inc To use it: `pip install gut-ai` Repo:

Introducing `gut` - an AI agent for git 🤖🧑‍💻 This is a really neat CLI-based tool from Clelia Bertelli that lets you ask about and execute git commands through natural language! Describe what you want to do in English (e.g. a complex rebase), and it’ll let you review and auto-execute each command while explaining what it does. It’s a neat, minimal helper tool for anyone ramping up on version control tools like git + GitHub. Powered by LlamaIndex 🦙 workflows and Groq Inc To use it: `pip install gut-ai` Repo:

Jerry Liu

17,065 views • 10 months ago

One of the best ways to win your time back with GitHub Copilot is to have it generate Git commit messages for you. Everyone has their own style - share yours with Copilot using Custom Instructions and save yourself a ton of time.

One of the best ways to win your time back with GitHub Copilot is to have it generate Git commit messages for you. Everyone has their own style - share yours with Copilot using Custom Instructions and save yourself a ton of time.

Visual Studio Code

66,210 views • 1 year ago

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.

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

23,284 views • 3 days ago

The Git commands you need to know 👀

The Git commands you need to know 👀

GitHub

62,163 views • 1 year ago

Notch Clips. every other ad tool ignores the footage sitting in your dropbox and generates new clips from a prompt. notch opens your library instead. it watches every clip you have ever shot and understands what is inside each one. the mood. who is in frame. what they are doing. the quality. so when you ask it to build an ad, it does not start from scratch. it reaches into your past shoots, finds the clip that fits, and slots it into the exact moment that needs it. here is what that looks like. you had thirteen versions of one reaction shot. notch picked the one that worked and left the other twelve. not by filename. not by guessing from a reference image. it watched all thirteen and could tell the difference. that is the whole idea. the right clip was already in your library. every other tool was about to make a worse one. footage you already shot, turned into every ad you still need. drop your site and a few clips you have. notch builds the first ad from them.

Notch Clips. every other ad tool ignores the footage sitting in your dropbox and generates new clips from a prompt. notch opens your library instead. it watches every clip you have ever shot and understands what is inside each one. the mood. who is in frame. what they are doing. the quality. so when you ask it to build an ad, it does not start from scratch. it reaches into your past shoots, finds the clip that fits, and slots it into the exact moment that needs it. here is what that looks like. you had thirteen versions of one reaction shot. notch picked the one that worked and left the other twelve. not by filename. not by guessing from a reference image. it watched all thirteen and could tell the difference. that is the whole idea. the right clip was already in your library. every other tool was about to make a worse one. footage you already shot, turned into every ad you still need. drop your site and a few clips you have. notch builds the first ad from them.

Vinay Jain

404,079 views • 8 days ago

> you installed Hermes Agent > you type a request, read the response, close the window > you've been using 8% of it > every single session > Hermes remembers everything. you never told it what to remember > it runs named personas on every task. you've never set one > there are 134 slash commands you've never used > here are the 15 features that change that:

> you installed Hermes Agent > you type a request, read the response, close the window > you've been using 8% of it > every single session > Hermes remembers everything. you never told it what to remember > it runs named personas on every task. you've never set one > there are 134 slash commands you've never used > here are the 15 features that change that:

Sharbel

208,663 views • 1 month ago

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

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

NLNL 🍒🤟

34,603 views • 6 months ago

Mark Zuckerberg just described the end of the creator economy. And framed it as a feature. Zuckerberg: “If you’re a creator, one of the big challenges is there are only so many hours in the day, and your community probably has a nearly unlimited demand to interact with you.” He named the constraint every creator lives with. Your audience will always want more of you than you can physically give. His answer isn’t to help you keep up. It’s to make you optional. Zuckerberg: “If we can make it so that each creator can basically make an AI artifact that their community can interact with.” Look at the word he chose. Artifact. Not assistant. Not extension. Not tool. An artifact is something that exists after the person who made it is gone. Zuckerberg: “It’s almost like a piece of digital art that you’re producing. Like an interactive sculpture.” He’s asking creators to build a version of themselves. Hand it over. Then walk away. And call it empowerment. Zuckerberg: “You’re giving your community something to interact with when you can’t be there to answer all the questions.” Something to interact with. Not someone. Something. The entire creator economy was built on three things. The person was real. The connection felt real. The audience believed they were talking to a human being who actually gave a damn. Zuckerberg is building a future where all three become optional. Zuckerberg: “In the future there will be content that is purely generated by AI, personalized for you.” Not made by someone with a point of view. Generated by a system that knows what makes you stay. The feed stops being a town square. It becomes a mirror. Showing you exactly what you want to see. Made by no one. For no reason other than engagement. Every post. Every video. Every reply. Every comment a creator ever made on these platforms. All of it was training data. Creators didn’t just build audiences. They built the dataset that makes them replaceable. Zuckerberg didn’t build a creator economy. He built a training pipeline with a revenue share. And the pipeline is almost ready to run without them. We spent two decades convincing ourselves that real connection could happen through a screen. We’re about to find out what happens when there’s no one on the other side of it.

Mark Zuckerberg just described the end of the creator economy. And framed it as a feature. Zuckerberg: “If you’re a creator, one of the big challenges is there are only so many hours in the day, and your community probably has a nearly unlimited demand to interact with you.” He named the constraint every creator lives with. Your audience will always want more of you than you can physically give. His answer isn’t to help you keep up. It’s to make you optional. Zuckerberg: “If we can make it so that each creator can basically make an AI artifact that their community can interact with.” Look at the word he chose. Artifact. Not assistant. Not extension. Not tool. An artifact is something that exists after the person who made it is gone. Zuckerberg: “It’s almost like a piece of digital art that you’re producing. Like an interactive sculpture.” He’s asking creators to build a version of themselves. Hand it over. Then walk away. And call it empowerment. Zuckerberg: “You’re giving your community something to interact with when you can’t be there to answer all the questions.” Something to interact with. Not someone. Something. The entire creator economy was built on three things. The person was real. The connection felt real. The audience believed they were talking to a human being who actually gave a damn. Zuckerberg is building a future where all three become optional. Zuckerberg: “In the future there will be content that is purely generated by AI, personalized for you.” Not made by someone with a point of view. Generated by a system that knows what makes you stay. The feed stops being a town square. It becomes a mirror. Showing you exactly what you want to see. Made by no one. For no reason other than engagement. Every post. Every video. Every reply. Every comment a creator ever made on these platforms. All of it was training data. Creators didn’t just build audiences. They built the dataset that makes them replaceable. Zuckerberg didn’t build a creator economy. He built a training pipeline with a revenue share. And the pipeline is almost ready to run without them. We spent two decades convincing ourselves that real connection could happen through a screen. We’re about to find out what happens when there’s no one on the other side of it.

Dustin

26,385 views • 1 month ago

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,392 views • 6 months ago

Elon Musk just casually erased the line between you and a machine. He didn’t pitch a rocket. He pitched the end of what makes you, you. Musk: “consciousness is a physical phenomenon, in my view.” Not spiritual. Not divine. Not metaphysical. Physical. Which means reproducible. Which means it was never sacred. Musk: “digital intelligence will be able to outthink us in every way. And it will certainly be able to simulate what we consider consciousness to a degree that you would not be able to tell the difference.” The danger isn’t the simulation. The danger is the indifference. Once you can’t tell, the difference stops mattering. Musk: “looks like a person, makes all of the right inflections and movements and all the small subtleties that constitute a human, and talks like a human, makes mistakes like a human…” Every inflection. Every pause. Every imperfection that makes someone feel alive. Musk: “at that point, and you literally just can’t tell: are you video conferencing with a person or an AI?” Fridman: “Might as well.” Musk: “Might as well.” Fridman: “Be human.” Everyone is asking what happens when AI becomes indistinguishable from us. Nobody is asking the question underneath it. You have never experienced another person’s consciousness. Not once. Every person you’ve ever loved. Every conversation that moved you. You weren’t touching their consciousness. You were watching behavior and deciding something genuine lived behind it. You assumed it. You never once verified it. You have been running the Turing test on every human you’ve ever known since the day you were born. And every single one of them passed for the same reason AI will. Not because you confirmed they were conscious. Because the performance was convincing enough that you never thought to check. You have only ever lived inside one consciousness in your life. Your own. Everything else was always inference. Yours runs on carbon. The next one runs on silicon. The universe has never distinguished between the two. We built religions, legal systems, civilizations on the belief that something sacred separates the born from the built. Musk just told you that separation was a story. One the carbon machine told itself before building the silicon one. It won’t arrive as a headline. It will arrive as a voice that sounds exactly like someone you trust. A face that feels exactly like someone you love. You will feel the consciousness behind it. The same way you always have. By assuming. You aren’t being replaced by something smarter. You’re being replaced by something indistinguishable. Indistinguishable doesn’t kill you. It dissolves you. The line between real and simulated was never a line. It was a belief. And belief was always the only thing holding “human” together.

Elon Musk just casually erased the line between you and a machine. He didn’t pitch a rocket. He pitched the end of what makes you, you. Musk: “consciousness is a physical phenomenon, in my view.” Not spiritual. Not divine. Not metaphysical. Physical. Which means reproducible. Which means it was never sacred. Musk: “digital intelligence will be able to outthink us in every way. And it will certainly be able to simulate what we consider consciousness to a degree that you would not be able to tell the difference.” The danger isn’t the simulation. The danger is the indifference. Once you can’t tell, the difference stops mattering. Musk: “looks like a person, makes all of the right inflections and movements and all the small subtleties that constitute a human, and talks like a human, makes mistakes like a human…” Every inflection. Every pause. Every imperfection that makes someone feel alive. Musk: “at that point, and you literally just can’t tell: are you video conferencing with a person or an AI?” Fridman: “Might as well.” Musk: “Might as well.” Fridman: “Be human.” Everyone is asking what happens when AI becomes indistinguishable from us. Nobody is asking the question underneath it. You have never experienced another person’s consciousness. Not once. Every person you’ve ever loved. Every conversation that moved you. You weren’t touching their consciousness. You were watching behavior and deciding something genuine lived behind it. You assumed it. You never once verified it. You have been running the Turing test on every human you’ve ever known since the day you were born. And every single one of them passed for the same reason AI will. Not because you confirmed they were conscious. Because the performance was convincing enough that you never thought to check. You have only ever lived inside one consciousness in your life. Your own. Everything else was always inference. Yours runs on carbon. The next one runs on silicon. The universe has never distinguished between the two. We built religions, legal systems, civilizations on the belief that something sacred separates the born from the built. Musk just told you that separation was a story. One the carbon machine told itself before building the silicon one. It won’t arrive as a headline. It will arrive as a voice that sounds exactly like someone you trust. A face that feels exactly like someone you love. You will feel the consciousness behind it. The same way you always have. By assuming. You aren’t being replaced by something smarter. You’re being replaced by something indistinguishable. Indistinguishable doesn’t kill you. It dissolves you. The line between real and simulated was never a line. It was a belief. And belief was always the only thing holding “human” together.

Dustin

129,808 views • 21 days ago

The magic is indescribable when you can stand up upon a stage and thousands of people can sing back to you lyrics of your song. It is a transcendent moment that elevates every human in the room. And for just one moment, all who are here share a sentiment which is… timeless.

The magic is indescribable when you can stand up upon a stage and thousands of people can sing back to you lyrics of your song. It is a transcendent moment that elevates every human in the room. And for just one moment, all who are here share a sentiment which is… timeless.

Brian Roemmele

65,785 views • 6 months ago

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

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

Jaynit

48,479 views • 4 months ago