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

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

На главную

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if...

271,119 просмотров • 5 месяцев назад •via X (Twitter)

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

Фото профиля Procyon Lotor
Procyon Lotor5 месяцев назад

And it’s not only about programming, it is true about every writing—less is more, concise is better.

Фото профиля Alan Morrison
Alan Morrison4 месяцев назад

The more nuanced argument is that you should take classes and most code out of the application layer and create graph-centric, (FAIR) versions in knowledge graphs (data layer) instead so 85 percent of code can be reusable. Malcolm Sparks describes here:

Фото профиля SCOTTY BEAM
SCOTTY BEAM5 месяцев назад

I'll check this video today broski, bookmarked

Фото профиля Ronald Grump
Ronald Grump4 месяцев назад

What if I want it to be polymorphic? Retarded take. Python developers are the worst

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

nice sharing!

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

Started planning around your release schedule

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

Thank you for pointing out that possibility.

Фото профиля Dave White - Black Cat Central Music
Dave White - Black Cat Central Music4 месяцев назад

Very true. Back when I started in the '90s I was typically asked how many lines of code did you write as if a large number was good or indicated the ability to manage a complex application. In fact, writing as few lines as possible, and re-use of objects is the better metric.

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

The best reason for a class is the maintenance of an algorithmic invariant. All others are manila folders.

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

Ha! Three fat cats with a trench coat 🤓

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

important things here

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

I don’t understand dev language but this was interesting

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

good video

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

> Most people add structure to feel like real engineers Most people are NOT engineers at heart. These include the ones working at the Big tech as well. Endless arguments for structured nonsense when a few lines would suffice things.

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

anyone can add abstraction line goes hard

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

interesting inform

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

classes are useful but people definitely reach for them way too early

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

less code is the real skill

Фото профиля Alpha Batcher
Alpha Batcher5 месяцев назад

i think it's will be interesting to listen something from Jack Diederich appreciate for the sharing

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

ronaldo has spent two decades making low probability moments look normal

Фото профиля cristal💎
cristal💎5 месяцев назад

if it has two methods and one is init it is a function fr

Фото профиля Emilia Tilley
Emilia Tilley5 месяцев назад

Sometimes the “class” is just a bag of functions with a jacket on 😅

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

saved, two methods one is init rule still hits

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

And I see this in crypto projects too - overcomplicating with classes when a function would do

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

Alpha interesting

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

just 27 minutes..

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

programming is still too hard for me

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

most interesting what we can see

Фото профиля Optimus Inu Diehard 🦾⚪️🦾
Optimus Inu Diehard 🦾⚪️🦾5 месяцев назад

We already knew this. But a proof is cool.

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

27 minutes of alpha

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

so old, but so good lecture

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

FR why make your life harder

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

Dario Amodei just told software engineers exactly how long they have. Six to twelve months. Amodei: “I have engineers within Anthropic who say I don’t write any code anymore. I just let the model write the code, I edit it, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.

Dustin

318,750 просмотров • 8 месяцев назад

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.

Dustin

82,914 просмотров • 8 месяцев назад

THIS IS F*CKING OBSCENE opus 5.5 got Fortnite running inside Minecraft and Minecraft running inside GTA 5, with nobody's permission and nobody's documentation three engines, three completely different ways in, and one of them has no way in at all THREE GAMES, THREE DIFFERENT WAYS IN → Minecraft is Java and ships a loader on purpose. that one is the front door. you write against an interface somebody meant for you to use → GTA 5 has no modding api and no front door. you get a compiled binary and nothing else, and the only route in is to read it → Fortnite is a live service with anti cheat sitting on top. there is no way in at all, and that single fact changes the entire job WHAT READING A BINARY ACTUALLY MEANS → no source, no comments, no function names. you recover what code does from what it is, which is the opposite direction from how it was written → the exact build gets pinned before anything else, because one patch moves every address underneath you, and a different version is a different game → nothing counts until it is confirmed inside the running process. launch it, play it, look at it. opus 5.5 does the reading, the pinning and the checking, and that loop is the part that used to be a team and a year WHAT THIS ACTUALLY CHANGES → reverse engineering was the most expensive skill in modding. one person, one binary, months of evenings, and the knowledge died with the project → now it is a loop that runs while you sleep, and what comes out of it is not a guess, it is something that got checked against the game while the game was running → so the hard question stopped being whether you can get into an engine. it is what you do once you are standing in three of them at once one layer was read out of a binary one came through the front door one was never touched at all, and it still had to land right

Roxx

195,977 просмотров • 28 дней назад

Larry Ellison just told every software engineer on Earth their job description is dead. Not evolving. Dead. Ellison: “The code that Oracle is writing, Oracle isn’t writing. Our AI models are writing.” This is not a startup demo. This is one of the largest infrastructure monopolies on the planet telling you it already replaced the people who built it. For fifty years, building software meant translating human intent into machine instructions. Line by line. Bug by bug. Sprint by sprint. That entire layer is gone. Ellison: “We don’t write the procedure. We declare our intent.” That sentence just made the entire engineering labor market flinch. The procedure was the job. The procedure was the paycheck. The procedure was what made a developer valuable. And now the machine does it without being asked twice. Ellison: “We just tell the model what we want the program to do, and then the AI comes up with a step-by-step process to actually do it.” You are no longer paid to build. You are paid to think. And most organizations have no idea how to evaluate that. The companies still hiring armies of developers to grind through codebases are paying salaries the machine already made worthless. Not in years. In seconds. When a company worth hundreds of billions hands the keyboard to the machine and tells you the output is better, the debate is not winding down. The debate is over. The enterprise that wins this decade does not write the best code. It removes the human from the process entirely and runs on intent alone. The programmers who survive are the ones who realize the craft is no longer typing. It is architecture. It is judgment. It is knowing what to build and why. Everything else now belongs to the machine. And the machine does not negotiate severance.

Dustin

537,001 просмотров • 7 месяцев назад

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

Elon Musk just said what every government on earth already knows and none will admit. Musk: “AI is moving 10 times faster than government, maybe more.” Not slightly faster. Ten times. And the gap compounds daily. Every institution ever built runs on the same architecture. Committees. Hearings. Drafts. Amendments. Votes. A process designed for a world that moved at the speed of human debate. That world is gone. The moment legislation is signed, the thing it was written for is already three generations obsolete. Law is becoming a monument to things that no longer exist by the time the ink is dry. Musk: “The one thing that the government can do is just issue people money.” The largest militaries ever assembled. The most sophisticated legal infrastructure in human history. The accumulated weight of ten thousand years of institutional evolution. Collapsed to a single remaining function. Printing checks. Not because they failed. Because the velocity of what is coming makes everything else they were built to do ornamental. Musk: “Nobody’s gonna starve is what I’m saying.” The floor rises. Survival becomes automatic. Nobody goes hungry. For ten thousand years, that would have been the finish line. It is not. It is the starting line of the hardest question the species has ever faced. Every civilization in history was organized around one brutal fact. The world needed your labor to function. You worked because you had to. You built because the alternative was death. Every economy, every identity, every reason to get out of bed was downstream of that single pressure. That pressure is being quietly removed. And what it leaves behind is not freedom. It is a vacuum. A check hits your account. Rent is covered. Food is handled. The base layer of existence is solved. But the thing that organized your time. Gave your effort weight. Made your life feel like it pointed somewhere. Gone. No government can legislate that back. No policy can manufacture it. Purpose is not a deposit. Identity is not a program. What you are for when the world no longer needs you to function is not a problem any institution was designed to answer. It is the first problem in history that belongs entirely to you. And while the rest of the world debates how to control what is coming, one person is doing the only thing that has ever mattered. Building what comes next.

Dustin

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