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…
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’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 トレンド
- 1. Josh Allen 40.4K posts
- 2. #GenshinSpecialProgram 7,707 posts
- 3. Texans 60.3K posts
- 4. Bills 149K posts
- 5. #FridayVibes 2,873 posts
- 6. Joe Brady 5,325 posts
- 7. Niger 46.8K posts
- 8. #MissUniverse 475K posts
- 9. #Ashes2025 25.9K posts
- 10. Troy 12.1K posts
- 11. OpenMind 50.3K posts
- 12. joon 13.2K posts
- 13. #StrayKids_DO_IT_OutNow 54.9K posts
- 14. Anderson 28K posts
- 15. McDermott 4,793 posts
- 16. FINAL DRAFT FINAL LOVE 1.32M posts
- 17. Beane 2,921 posts
- 18. Infinit 82.7K posts
- 19. México 586K posts
- 20. STRAY KIDS DO IT IS DIVINE 57K posts
Something went wrong.
Something went wrong.