Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • OO design naturally manages complexity OOP naturally introduces unnecessary complexity. Commented Sep 15, 2015 at 21:32
  • "Unnecessary complexity" reminds me of priceless comments from co-workers such as "oh, that's too many classes." Experience tells me that the juice is worth the squeeze. At it's best I see virtually entire classes with methods 1-3 lines long and with every class doing it's part complexity of any given method is minimized: A single short LOC comparing two collections and returning the duplicates - of course there is code behind that. Don't confuse "a lot of code" to complex code. In any case, nothing is free. Commented Sep 15, 2015 at 23:57
  • 1
    Lots of "simple" code that interacts in a complicated way is WAY worse than a small amount of complex code. Commented Sep 16, 2015 at 0:00
  • 1
    The small amount of complex code has contained complexity. There's complexity, but only there. It doesn't leak out. When you have a whole lot of individually simple pieces that work together in a really complex and difficult to understand way that's much more confusing because there are no borders or walls to the complexity. Commented Sep 16, 2015 at 0:01