Re:Too many layers of abstraction -- worthless crap (2007)
by ntoshev on Thursday September 01, 2011 @04:52AM
(#2949179)
Well, #2 should be "the code is a mess" which sometimes is a result from too many layers of abstraction, sometimes from improper abstractions, sometimes from lack of abstractions. In my experience novices underengineer, while experienced coders do tend to overengineer.
[ Parent
| on HN ]
Re:Too many layers of abstraction -- worthless crap (2007)
by acqq on Thursday September 01, 2011 @05:07AM
(#2949225)
No, it's not "a mess." People who write it follow a lot of rules. The problem is, following rules just "because it should be done so" and uncritically applying them leads to very weird things (^) I believe you haven't seen what a lot of programmers working under bad lead can produce in a year of two out of the simple goals...
Really experienced programmers don't "overengineer."
(^) It looks like: "public class RecursiveFactorialImplementation implements FactorialAlgorithm" from: http://news.ycombinator.com/item?id=2143310