Usually employers will take a chance on some one who is inexperienced if they can prove they are a passionates programmer, show that that you have some initiative. Work on your own projects, or at least join discussion groups in your desired field such as meetups.
I have had to deal with lots of different methodologies about documentation practices and what i found is that the best documentation is code. Self documenting code and tests usually stay up to date and are harder to overlook.
This is silly, and dangerous (and not because of the tsunami). The plant will be exposed to hurricanes/typhoons, as well as be inaccessible in case of emergency, and is there a grantee that the spent fuel won't get into the water when a catastrophe occurs?
Lets not get into the faults of Java and inheritance this thread might devolve into something it shouldn't :).
But its a good idea to do some of this stuff where and WHEN its appropriate. You can design a space shuttle to go to the grocery store doesn't mean you should.
I have seen my fare share of useless hard to understand and over engineered code in C, Groovy, Java and Lisp
A good book about this by Joshua Kerievsky is Refactoring To Patterns he talks exactly about this, the dangers of using patterns and the dangers of not (yes he uses Java in his examples)
I am very very confused what this post has to do with Java? It has everything to do with premature optimization and implementation of Design Patterns unnecessarily... And since Design Patterns are not language specific the title of this post is wrong and misleading even the conclusion that the author tries to draw up is of dubious merit ..... The only part of the post that makes this specific to Java is the comment that the factorial function must be wrapped in a class.
Err Ok... you have a point to make but it is not what you think it is. :) It has nothing to do with Java Programmers. It has everything to do with premature optimization and implantation of Design Patters for the sake of Implementing a Design Pattern ... for more information on what I am trying to get at please read Refactoring to Patterns [http://www.informit.com/store/product.aspx?isbn=013265119X]