Загрузка видео...
Не удалось загрузить видео
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... show more
271,119 просмотров • 5 месяцев назад •via X (Twitter)
Комментарии: 32

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

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:

I'll check this video today broski, bookmarked

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

nice sharing!

Started planning around your release schedule

Thank you for pointing out that possibility.

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.

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

Ha! Three fat cats with a trench coat 🤓

important things here

I don’t understand dev language but this was interesting

good video

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

anyone can add abstraction line goes hard

interesting inform

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

less code is the real skill

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

ronaldo has spent two decades making low probability moments look normal

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

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

saved, two methods one is init rule still hits

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

Alpha interesting

just 27 minutes..

programming is still too hard for me

most interesting what we can see

We already knew this. But a proof is cool.

27 minutes of alpha

so old, but so good lecture

FR why make your life harder

