News for hackers. Stuff that matters.
Re:Software Design Patterns Are Not Goals, They Are Tools by deong on Thursday May 19, 2016 @10:27AM (#11730444)
No one is against coding structure, or even "best practices", if you interpret it as meaning the thing someone fluent in English but with no background in software development would understand it to mean. The problem is that "best practices" in our industry has become a specific term meaning "overly complicated by a factor of about seven, but with enough meaningless jargon invented to describe it that no one feels comfortable saying the emperor is in fact naked".
Re:Software Design Patterns Are Not Goals, They Are Tools by lgunsch on Thursday May 19, 2016 @01:02PM (#11731667)
I would agree with that definition has become the new interpretation of "best practices". However, in my 5 year career I have seen the majority of solutions under-engineered. That is much more of an issue these days than over-engineering.
Re:Software Design Patterns Are Not Goals, They Are Tools by Benjammer on Thursday May 19, 2016 @02:45PM (#11732621)
>majority of solutions under-engineered. That is much more of an issue these days than over-engineering.

Couldn't agree more.

Re:Software Design Patterns Are Not Goals, They Are Tools by Benjammer on Thursday May 19, 2016 @11:07AM (#11730789)
I totally agree with you, I just think that the ideas being discussed in this thread have a ton of nuance and they can be dangerous to introduce to a junior developer who doesn't quite realize the difference between the idea of "complexity" we're talking about here and the fact that he shouldn't be copy-pasting boilerplate code all over the app and copy-pasting directly from StackOverflow without any editing or integration of the code.