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. Travis Head 13.3K posts
- 2. Caleb Love 2,971 posts
- 3. Mamdani 477K posts
- 4. Marjorie Taylor Greene 73.5K posts
- 5. Sengun 8,824 posts
- 6. Suns 21.5K posts
- 7. Morgan Geekie N/A
- 8. Kerr 5,341 posts
- 9. Norvell 3,578 posts
- 10. Lando 50K posts
- 11. UNLV 2,273 posts
- 12. #SmackDown 48.2K posts
- 13. Collin Gillespie 4,139 posts
- 14. #DBLF2025 13.9K posts
- 15. Blazers 4,103 posts
- 16. Wolves 16.8K posts
- 17. The View 101K posts
- 18. Florida State 10.9K posts
- 19. joshua 102K posts
- 20. Rockets 17K posts
Something went wrong.
Something went wrong.