10 signs you are a Java wanna be
1 — You have more static methods than non-static methods
2 — You instantiate a sub-class from within that class’s superclass
3 — You use an interface as a method parameter, but then cast it to an implementation
4 — You use an interface for a method parameter, but require it to be a specific implementation
5 — It becomes harder and harder to use your well modularized components, so you start merging everything together (i.e. tight coupling)
6 — You say Java can’t scale when your app runs slow on fast machines
7 — Your beautiful web app is coded entirely in JSPs
8 — You have no clue as to what overloaded methods are and as a result you have tons of methods that all look suprisingly similar with different arguments
9 — You can’t read a stack trace
10 — You aren’t sure what a stack trace is
Did I miss anything here?
![](http://a1.twimg.com/profile_images/83517938/projecter_logo_125x125_2_normal.png" rel="image){kind=logo}
Don’t miss anything, subscribe!
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
You are lame ! Go fcuck your self you lamo fucker