avg_gopher's profile picture. Average at most things. Opinions are mid.

average gopher

@avg_gopher

Average at most things. Opinions are mid.

Here is an even shorter post on inheritance: You do not need inheritance in your code. Ever. Pretend it does not exist. There are much nicer ways to structure code.

Every developer hits this moment. Your code looks fine, but something feels off. Classes behave in weird ways. Bugs appear from nowhere. Nothing is consistent. Most of the time the real issue is broken inheritance. I wrote a quick post explaining the Liskov Substitution…

abhip_me's tweet image. Every developer hits this moment.
Your code looks fine, but something feels off.
Classes behave in weird ways. Bugs appear from nowhere. Nothing is consistent.

Most of the time the real issue is broken inheritance.

I wrote a quick post explaining the Liskov Substitution…


OOP is a brain disease that could be cured only by spending some time coding in Go, Zig or just C

I was in a debate with a tech lead for using all these layers in java with no meaning just a whole class with a whole file just to call another function, and how this was entirely very stressful and overwhelming, i would spend less days and ship if it is not opp



That’s a fair point, Omarchy looks great, but the only successful way forward is realizing you’re now owning all the bash scripts it comes with.

I’m a dhh fan, but guys. do you *remember* rails? yall wanna tinker for days on your OS go ahead, but there’s no way this thing is stable over the course of a decade. that’s just not how this man works lol.



I’ll never get how #arch is considered a good idea. It claims to be minimal, yet provides zero mechanisms to persist your own config. Also, the rolling release model is borderline insane if you actually care about stability.


United States Tendências

Loading...

Something went wrong.


Something went wrong.