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

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

На главную

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

239,491 просмотров • 4 месяцев назад •via X (Twitter)

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

Фото профиля アキラ
アキラ4 месяцев назад

Interesting experiment! Shows the power of understanding fundamentals.

Фото профиля slash1s
slash1s4 месяцев назад

that’s the point yes

Фото профиля アキラ
アキラ4 месяцев назад

Absolutely, understanding the main point is crucial.

Фото профиля slash1s
slash1s4 месяцев назад

join my tg for the actual alpha on ai, financial markets and coding ->

Фото профиля Kaivalya Apte - The Geek Narrator
Kaivalya Apte - The Geek Narrator4 месяцев назад

@tlberglund you haven’t changed a bit 🙂 or maybe just a couple of bits 🙂

Фото профиля writer of strange software
writer of strange software4 месяцев назад

I’ve been doing this for a few years. A five years ago I wrote my own Git server to accelerate it. Two years ago I made it fully streamable so that the server could react in milliseconds to a pushed update and I could target very sparse subsets of what was in my program generator’s object model.

Фото профиля 𝗢𝗠𝗘𝗚𝗔
𝗢𝗠𝗘𝗚𝗔4 месяцев назад

most devs panic on rebase five percent read objects and just fix it

Фото профиля slash1s
slash1s4 месяцев назад

🫡 facts

Фото профиля 0xbobaa
0xbobaa4 месяцев назад

smart content

Фото профиля slash1s
slash1s4 месяцев назад

haha yes

Фото профиля Ridark
Ridark4 месяцев назад

Sound mixing made the quiet moments hit harder

Фото профиля slash1s
slash1s4 месяцев назад

🤔

Фото профиля Gipp 🦅
Gipp 🦅4 месяцев назад

I think it's very difficult to do

Фото профиля Terry Bui
Terry Bui4 месяцев назад

そのコミットは本当に驚きですね!git addやgit commitはただの外皮であり、あなたが以前に明らかにしたことがないデータベースを覆っているだけです。あなたが行ったすべてのコミットは、Gitがスナップショットを撮って、指紋を保存しているだけです。それらのオブジェクトのグラフを見ることができると、恐れていたコマンドはもはや恐ろしくはなりません。

Фото профиля exodus
exodus4 месяцев назад

His work deserves a national award!

Фото профиля Tyler Mills
Tyler Mills4 месяцев назад

this video is like 14 years old lol

Фото профиля starmex
starmex4 месяцев назад

every team has one person who fixes git when it breaks, this talk quietly makes you that person

Фото профиля Nekt0
Nekt04 месяцев назад

Let’s go

Фото профиля EMOTION CRYPTO
EMOTION CRYPTO4 месяцев назад

Added this alpha to my bookmarks

Фото профиля Gia huy
Gia huy4 месяцев назад

次のコミットは、本当に完了しており、決して「git add」や「git commit」を入力したことはありません。それらのコマンドは、ごく稀に日常的に接するものを露出させただけの薄いカバーであり、まだ一度も開かれたことのないデータベースを覆っていることを証明しています。

Фото профиля cvxv666
cvxv6664 месяцев назад

bookmarked, this guy a legend fr

Фото профиля ViceSol
ViceSol4 месяцев назад

This is the line between juniors who just copy-paste 'git push -f' and seniors who actually understand Directed Acyclic Graphs. Once you manually write a blob into .git/objects and update a ref by hand, the tool is never scary again. Essential watch for the AI agent era

Фото профиля Atenov int.
Atenov int.4 месяцев назад

But can you really read the object graph in your head after using git for years

Фото профиля Legion
Legion4 месяцев назад

AI writing is becoming intolerable

Фото профиля Bizzi
Bizzi4 месяцев назад

Wow, I will watch bro

Фото профиля liosaky
liosaky4 месяцев назад

Gitの本質を知ることが大切です。グラフを読んでみましょう。

Фото профиля Saberin Samarat
Saberin Samarat4 месяцев назад

Thanks for sharing

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

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓

slash1s

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