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?

  • Valmond@lemmy.world
    1·
    7 hours ago

    So show me two compatible systems where the int has different sizes.

    This is folklore IMO, or incompatible anyways.

      • Valmond@lemmy.world
        1·
        3 hours ago

        Okay, then give me an example where this matters. If an int hasn’t the same size, like on a Nintendo DS and Windows (wildly incompatible), I struggle to find a use case where it would help you out.

        • Feyd@programming.dev
          2·
          3 hours ago

          You can write code that is dependent on using a specific width of data type. You can compile code for different platforms. I have no idea what you’re thinking when you say “wildly incompatible”, but I guarantee you there is code that runs on both Nintendo DS and Windows.