Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

slash1sol's profile picture

slash1s

8,274 subscribers

37,059 görüntüleme • 6 gün önce •via X (Twitter)

KomediEğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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

235,464 görüntüleme • 14 gün önce

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.
0:34

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

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓
31:26

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓

slash1s

255,131 görüntüleme • 10 gün önce

TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED 42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist. -> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you. Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening. Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster. Most people use 5% of git and call it a day. This is the other 95% nobody showed you. Bookmark it and Watch today ↓
42:40

TWO ENGINEERS SHOWED THE GIT TRICKS THAT MAKE PEOPLE THINK YOU'RE A WIZARD -- THE ONES 95% OF DEVELOPERS HAVE NEVER ONCE TOUCHED 42 minutes from Johan Abildskov and Jan Krag, bending git with custom configs, attributes and hooks most people don't even know exist. -> The moment it lands, git stops being four commands you repeat in fear. The same tool you've used for years turns out to have a whole layer built to bend to you. Hooks that run your checks before a bad commit ever lands. Attributes that end the "it works on my machine" merge wars. Config that makes the painful parts just stop happening. Memorizing commands was never the ceiling -> shaping git to do the work for you is. And while everyone else fights the tool by hand, the person who set it up right is shipping clean three times faster. Most people use 5% of git and call it a day. This is the other 95% nobody showed you. Bookmark it and Watch today ↓

slash1s

103,981 görüntüleme • 7 gün önce

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓
1:24:59

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓

slash1s

452,989 görüntüleme • 11 gün önce

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

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

slash1s

27,681 görüntüleme • 18 gün önce

HARVARD HAS A FULL 53-MIN GIT LECTURE FROM DAVID MALAN BECAUSE 90% OF NEW DEVELOPERS STILL DON'T KNOW WHAT A COMMIT ACTUALLY IS 53 minutes of no-nonsense version control from the instructor whose course became the largest class in Harvard history. -> The moment you watch it, you realize why "I'll just push to main" is the fastest way to get fired in your first month. Every junior engineer in 2026 is expected to handle Git on day one - no excuses, no Stack Overflow, no AI hand-holding. Git isn't a "senior dev thing" anymore -> it's the literacy test for being in the room. The agent can ship the feature in 5 minutes. Recovering the repo it broke takes 5 hours - and only if you actually understand what happened. Don't forget to bookmark it.
53:11

HARVARD HAS A FULL 53-MIN GIT LECTURE FROM DAVID MALAN BECAUSE 90% OF NEW DEVELOPERS STILL DON'T KNOW WHAT A COMMIT ACTUALLY IS 53 minutes of no-nonsense version control from the instructor whose course became the largest class in Harvard history. -> The moment you watch it, you realize why "I'll just push to main" is the fastest way to get fired in your first month. Every junior engineer in 2026 is expected to handle Git on day one - no excuses, no Stack Overflow, no AI hand-holding. Git isn't a "senior dev thing" anymore -> it's the literacy test for being in the room. The agent can ship the feature in 5 minutes. Recovering the repo it broke takes 5 hours - and only if you actually understand what happened. Don't forget to bookmark it.

slash1s

251,959 görüntüleme • 24 gün önce

AN MIT RESEARCHER PROVED GIT ISN'T HARD BECAUSE YOU'RE BAD AT IT -- IT'S HARD BECAUSE IT WAS DESIGNED THAT WAY 27 minutes from a PhD researcher in MIT's Software Design Group, using actual design theory to show why the tool that confuses everyone confuses everyone for a reason. -> The moment it lands, years of feeling stupid evaporate. The gap between what git's commands say and what they actually do was never in your head. It's baked into the tool. He maps the difference between what you think a command does and what git really does underneath. Once you see that gap, the confusion finally has a name and it stops being yours to carry. Struggling with git was never a skills issue -> it's a design issue, and knowing where the model lies to you is what turns panic into control. And as AI agents fire off commits and rebases you didn't write, the person who understands where git misleads is the one who untangles the mess. You were never bad at git. You were just never shown where it was built to trip you. Bookmark & Watch it today ↓
26:35

AN MIT RESEARCHER PROVED GIT ISN'T HARD BECAUSE YOU'RE BAD AT IT -- IT'S HARD BECAUSE IT WAS DESIGNED THAT WAY 27 minutes from a PhD researcher in MIT's Software Design Group, using actual design theory to show why the tool that confuses everyone confuses everyone for a reason. -> The moment it lands, years of feeling stupid evaporate. The gap between what git's commands say and what they actually do was never in your head. It's baked into the tool. He maps the difference between what you think a command does and what git really does underneath. Once you see that gap, the confusion finally has a name and it stops being yours to carry. Struggling with git was never a skills issue -> it's a design issue, and knowing where the model lies to you is what turns panic into control. And as AI agents fire off commits and rebases you didn't write, the person who understands where git misleads is the one who untangles the mess. You were never bad at git. You were just never shown where it was built to trip you. Bookmark & Watch it today ↓

slash1s

137,732 görüntüleme • 9 gün önce

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):
1:27

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 görüntüleme • 2 yıl önce

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

224,685 görüntüleme • 17 gün önce

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

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

slash1s

380,691 görüntüleme • 15 gün önce

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓
1:01:03

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓

slash1s

13,073 görüntüleme • 5 gün önce

Your trading strategy didn't break. The market it was built for quietly stopped existing. Read that twice. It's most of why 89% of retail finished 2025 in the red. There's now an app that does the entire job of a $400,000 quant. You type a trading idea in plain English. It writes the code, backtests 5 years in 12 seconds, runs thousands of simulations, and tells you cold whether your edge is dead or the regime just changed. No code. No Python. No $25,000 terminal. 20,000 already inside. Waitlist stops at 25,000: That distinction is the whole game, and you never had a way to see it. Every strategy is a bet that one thing stays true. Momentum bets trends continue. Mean reversion bets ranges hold. When the regime flips, the assumption dies and your strategy bleeds with nothing wrong in the code. You stare at the logic for a month and never find the bug, because there isn't one. So you delete it, or refit it to the last drawdown and build something that would have survived the pain you already felt and nothing coming next. The desks never had that problem. 92% of institutional volume is automated. Only 45% of retail is. They test 100 strategies for every 1 you test by hand, and kill 97 of them on purpose, because they can tell a dead edge from a normal drawdown. Now that exact loop costs $0. One hypothesis used to cost a fund $87,500 to test. With Horizon you get unlimited, in seconds, and a winner deploys live in 90 seconds and runs without your hands on it.
0:40

Your trading strategy didn't break. The market it was built for quietly stopped existing. Read that twice. It's most of why 89% of retail finished 2025 in the red. There's now an app that does the entire job of a $400,000 quant. You type a trading idea in plain English. It writes the code, backtests 5 years in 12 seconds, runs thousands of simulations, and tells you cold whether your edge is dead or the regime just changed. No code. No Python. No $25,000 terminal. 20,000 already inside. Waitlist stops at 25,000: That distinction is the whole game, and you never had a way to see it. Every strategy is a bet that one thing stays true. Momentum bets trends continue. Mean reversion bets ranges hold. When the regime flips, the assumption dies and your strategy bleeds with nothing wrong in the code. You stare at the logic for a month and never find the bug, because there isn't one. So you delete it, or refit it to the last drawdown and build something that would have survived the pain you already felt and nothing coming next. The desks never had that problem. 92% of institutional volume is automated. Only 45% of retail is. They test 100 strategies for every 1 you test by hand, and kill 97 of them on purpose, because they can tell a dead edge from a normal drawdown. Now that exact loop costs $0. One hypothesis used to cost a fund $87,500 to test. With Horizon you get unlimited, in seconds, and a winner deploys live in 90 seconds and runs without your hands on it.

cvxv666

39,933 görüntüleme • 5 gün önce

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.
0:40

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

405,527 görüntüleme • 19 gün önce

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

250,454 görüntüleme • 28 gün önce

"When you perpetrate an apartheid, when you commit a genocide, and then when you support it all in the name of the Jewish people — THAT is what causes antisemitism to be on the rise — not the opposition of those horrific crimes." Antizionism ≠ antisemitism!
1:41

"When you perpetrate an apartheid, when you commit a genocide, and then when you support it all in the name of the Jewish people — THAT is what causes antisemitism to be on the rise — not the opposition of those horrific crimes." Antizionism ≠ antisemitism!

AIPAC Tracker

16,387 görüntüleme • 1 yıl önce

An entire empire was overthrown over a two percent tax on a breakfast beverage. Look at what you tolerate now. You are taxed when you earn it. Taxed when you spend it. Taxed when you save it. Taxed when you invest it. And when you die, they tax whatever is left. That is not a system. That is a harvest. You commute in a car you paid sales tax to buy. You drive it on roads you were already taxed to build. You fill it with gas taxed by the gallon. When you sell that car, the next buyer pays sales tax on it again. The same car. Taxed every time it changes hands. You arrive at a job where your salary is cut before it ever touches your hands. If you work for yourself, you pay both sides. Two people on paper. Neither one keeps what they earned. Then you go home. Every bill you open has a government standing behind it with its hand out. You buy a house with money they already took their share of. Then they charge you property tax on it every year for the rest of your life. You want to renovate your own kitchen. You need a permit. You want to build a deck on your own land. You need a permit. You pay for the property. Then you pay for permission to use it. Stop paying property tax and they seize your home. Not because you missed a mortgage payment. Because you missed a payment to the government for the privilege of keeping what is already yours. You do not own your home. You rent it from the state. If you leave something behind for your children, they are taxed on what you were already taxed to earn. The same wealth. Taxed at every stage of your life. Then taxed one final time because you had the audacity to die. They found a way to monetize your absence. We are told this is the price of civilization. It is not. It is architecture. The most effective prison ever built is the one where the inmates believe they are free. They did not take your freedom. They priced you out of it. If you kept the full value of your labor, you would be free within years. Not decades. Years. The system cannot allow that. A machine built on consumption needs a consumer that never stops. You did not sign a social contract. You were assigned one. Now pay attention. They spent decades perfecting the extraction of your productivity. Now they are building the technology to replace you. AI is not coming for your job because corporations are greedy. It is coming because a system that already takes half your output just realized it can take all of it. Without needing you in the equation. You were never the point of this arrangement. You were the input. And the moment they engineer a cheaper one, you become a rounding error on a quarterly earnings call. They did not build AI to free you. They built it to finish what the tax code started. It was never about the tea. It was about the precedent. Today we hand over half our waking lives and thank them for the potholes. You do not live in a free economy. You live in a subscription you never signed up for. And the penalty for canceling is everything you have.
0:57

An entire empire was overthrown over a two percent tax on a breakfast beverage. Look at what you tolerate now. You are taxed when you earn it. Taxed when you spend it. Taxed when you save it. Taxed when you invest it. And when you die, they tax whatever is left. That is not a system. That is a harvest. You commute in a car you paid sales tax to buy. You drive it on roads you were already taxed to build. You fill it with gas taxed by the gallon. When you sell that car, the next buyer pays sales tax on it again. The same car. Taxed every time it changes hands. You arrive at a job where your salary is cut before it ever touches your hands. If you work for yourself, you pay both sides. Two people on paper. Neither one keeps what they earned. Then you go home. Every bill you open has a government standing behind it with its hand out. You buy a house with money they already took their share of. Then they charge you property tax on it every year for the rest of your life. You want to renovate your own kitchen. You need a permit. You want to build a deck on your own land. You need a permit. You pay for the property. Then you pay for permission to use it. Stop paying property tax and they seize your home. Not because you missed a mortgage payment. Because you missed a payment to the government for the privilege of keeping what is already yours. You do not own your home. You rent it from the state. If you leave something behind for your children, they are taxed on what you were already taxed to earn. The same wealth. Taxed at every stage of your life. Then taxed one final time because you had the audacity to die. They found a way to monetize your absence. We are told this is the price of civilization. It is not. It is architecture. The most effective prison ever built is the one where the inmates believe they are free. They did not take your freedom. They priced you out of it. If you kept the full value of your labor, you would be free within years. Not decades. Years. The system cannot allow that. A machine built on consumption needs a consumer that never stops. You did not sign a social contract. You were assigned one. Now pay attention. They spent decades perfecting the extraction of your productivity. Now they are building the technology to replace you. AI is not coming for your job because corporations are greedy. It is coming because a system that already takes half your output just realized it can take all of it. Without needing you in the equation. You were never the point of this arrangement. You were the input. And the moment they engineer a cheaper one, you become a rounding error on a quarterly earnings call. They did not build AI to free you. They built it to finish what the tax code started. It was never about the tea. It was about the precedent. Today we hand over half our waking lives and thank them for the potholes. You do not live in a free economy. You live in a subscription you never signed up for. And the penalty for canceling is everything you have.

Dustin

27,624 görüntüleme • 1 ay önce

This might be the TUI of the year ⭐ 🎬 gitlogue — A cinematic Git commit replay tool for the terminal. ⚡ Watch commits unfold with typing animations, syntax highlighting and a live-updating file tree. 🤯 Watch your repo code itself. 🦀 Written in Rust & built with Ratatui ⭐ GitHub: #rustlang #ratatui #tui #git #commits #replay #terminal #screensaver
2:40

This might be the TUI of the year ⭐ 🎬 gitlogue — A cinematic Git commit replay tool for the terminal. ⚡ Watch commits unfold with typing animations, syntax highlighting and a live-updating file tree. 🤯 Watch your repo code itself. 🦀 Written in Rust & built with Ratatui ⭐ GitHub: #rustlang #ratatui #tui #git #commits #replay #terminal #screensaver

Orhun Parmaksız 👾

32,130 görüntüleme • 7 ay önce

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 ↓
36:09

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

190,587 görüntüleme • 13 gün önce

Here’s a quick git dev challenge: you've got three edits, two adds, and one commit. Looks straightforward, but which version actually ends up in the repo? Watch the video and share your answer in the comments.
0:31

Here’s a quick git dev challenge: you've got three edits, two adds, and one commit. Looks straightforward, but which version actually ends up in the repo? Watch the video and share your answer in the comments.

Google for Developers

15,034 görüntüleme • 2 ay önce