So developers try to future-proof their project by using those patterns everywhere.
Something I've seen a lot (and been guilty of myself) is trying to fix the problems of past projects in new projects before they crop up.A better solution is to not be afraid of refactoring (tests help here) so you can solve the problems when they become a problem, not create complication before.
Re:Fizz Buzz: Enterprise Edition
by edwinnathaniel on Monday March 18, 2013 @03:08PM
(#5396432)
> Now for the bitchy part, why does no one ever speaks about the good sides of Java?
Cause at some point most of them got tired to preach about Java and continue to do great work vs worrying what other people think.
Look around: NetFlix, Yammer, Twitter, Google are all using Java to power either their infrastructure or apps. Nobody blogs about it because "It Works" ;)
The rest blogs how they keep jumping between wagons :P
this joke thing isn't really about Java as a language though. its about a very weird/bad and surprisingly common design anti-pattern. Java was used to do this joke because its utterly typical for this type of work, but certainly you can have this kind of disgusting enterprisey garbage in just about any programming language.
nobody makes jokes at the expense of well written Java software because its well written. we all know that the language is perfectly fine, and in alot of ways quite good, when it is used by sensible engineers.
Re:Fizz Buzz: Enterprise Edition
by themstheones on Monday March 18, 2013 @02:11PM
(#5396021)
Because people who know the good side of java have jobs.
I generally go by the saying, baring any existing req's that abstraction patterns would help with:
'Code to use, Refactor to re-use'
Re:Fizz Buzz: Enterprise Edition
by charleslmunger on Tuesday March 19, 2013 @02:53AM
(#5399342)
Public fields for immutable objects are fine, but adding thread safety later is difficult if you use them.
My best guess would be that you often need to refactor you code to include some of the patterns showcased in the repo (factories, for instance). So developers try to future-proof their project by using those patterns everywhere. This is obviously a terrible idea.
Now for the bitchy part, why does no one ever speaks about the good sides of Java?