Camel Case Java

I have worked with JSF for almost 4 years. First time when I had a chance to work with GWT, I was very excited. Like many Java developers I was like 'Wow I don't need to play with those bloody tags and elements and now it's pure Java code!!!'... I was so happy but my happiness didn't last very long. Programming is my passion. I hate writing codes that become a mess later and unfortunately this is what will eventually happen with GWT. The thing is you can't rely on reviews and features of a software or an API, in action everything goes different way. Specially when it comes to large scaled application and in an environement where everything is urgent and importnat... well, I think all software companies are the same in this regard... The fact is that in a team of developers not every one cares about best practices, design patterns and even if you have very experienced designer, solution architect etc, still you can't force the team to deve

Hi My name is Mohammad. I am a passionate Java developer. When I was in university, I was very interested in Borland Delphi and Turbo C++ they were hot at those ages but I ended up with my first job as Oracle Developer. I was lucky because Delphi was about to die and now we can call it an ancient programming language! It is back to its hometown: Delphi Temple :) So after two years working with Oracle Form Builder and Oracle database, I attracted to Java. So first thing I learned was Apache Struts 1.1. It was awesome however now every body smiles when you mention it :) Very soon I switched to JSF and JBoss. But they were very young at that time. I also worked with Beehive from Apache which nobody may heard about it :) I worked with Apache Lucene, JSF and JBoss Seam for about two years and then I packed my bag to work in back end. I love back end programming! My best years of working was in a Banking software company which I had oppurtunity to design and develop some big applic