As a Java engineer in the web development industry for several years now, having heard multiple times that X is good because of SOLID principles or Y is bad because it breaks SOLID principles, and having to memorize the “good” ways to do everything before an interview etc, I find it harder and harder to do when I really start to dive into the real reason I’m doing something in a particular way.
One example is creating an interface for every goddamn class I make because of “loose coupling” when in reality none of these classes are ever going to have an alternative implementation.
Also the more I get into languages like Rust, the more these doubts are increasing and leading me to believe that most of it is just dogma that has gone far beyond its initial motivations and goals and is now just a mindless OOP circlejerk.
There are definitely occasions when these principles do make sense, especially in an OOP environment, and they can also make some design patterns really satisfying and easy.
What are your opinions on this?
I did have a couple of years of gamedev under the belt, but only j2me java mobile games, so laying my hands on a nintendo dev kit was one of those one in a lifetime highs for me. Still get a tingle when I think about it ☺️.
You’re right about todays landscape though 😑, between abusing A to AAA companies, dark patterns and microtransactions 🤢. Such a shame. I should get into indie games more but they all feel like they were made for unity/UE, so they all feel a bit the same (where are syrategy games, spinoffs off Worms, lemmings, …). But maybe I’m missing out, there is so much rubbish to sift through.
Cheers!