[websitescenes]

Usually when I assess code as over complicated it is because the engineer is solving the problem indirectly. Very often I see people focus on the perceived constraints of a problem instead of solving the actual problem. These same people often get married to their approach and resist other ways because they have already invested so much time in their current approach. We never know less than we know today and to not change your approach based on new information will undoubtedly result in spaghetti code, I mean “over engineered code”.

It’s incredible how simple things can be if you think about them creatively enough.

[marginalia_nu]

I dunno, I often feel things get complicated when such an incredibly simple solution encounters a set of additional requirements.

They often tend to be sort of bolted on, rather than integrated neatly by rewriting the thing to a new simple solution that caters to both requirement sets.

The problem is more like Katamari Damacy-code than spaghetti code.

[websitescenes]

The more I think about this, it’s actually the same problem I described above. The issue is a failure to evolve based on new information.

[websitescenes]

Fair point, I’ve experienced that as well.