Getters and setters are superfluous in most cases, because you do not actually want to hide complexity from your users.
To use the usual trivial example : if you change your circle’s circumference from a property to a function, I need to know ! You just replaced a memory access with some arithmetic ; depending in my behaviour as a user this could be either great or really bad for my performance.
99% of code is too complicated for what it does because of principles like SOLID, and because of OOP.
Algorithms can be complex, but the way a system is put together should never be complicated. Computers are incredibly stupid, and will always perform better on linear code that batches similar operations together, which is not so coincidentally also what we understand best.
Our main issue in this industry is not premature optimisation anymore, but premature and excessive abstraction.
As a vegan, this has been my main meal because I’m pretty lazy (usually wrapped in a tortilla with guacamole, but I also eat it plain)
The gas issues are only a problem for a few days / weeks until your gut biome adjusts !
No. These principles are supposedly designed to help those inexperienced programmers, but in my experience, they tend to do the opposite.
The rules are too complicated, and of dubious usefulness at best. Inexperienced programmers really need to be taught to keep things radically simple, and I don’t mean “single responsibility” or “short functions”.
I mean “stop trying to be clever”.