javacodegeeks

http://www.javacodegeeks.com/2011/06/android-game-development-tutorials.html

http://www.javacodegeeks.com/2011/06/grow-up-java-proposing-java-desktop.html

http://www.javacodegeeks.com/2011/06/zero-downtime-deployment-and-rollback.html

http://www.javacodegeeks.com/2011/06/poor-mans-approach-in-practice.html

http://www.javacodegeeks.com/2011/04/app-engine-capabilities-namespaces-api.html

http://www.javacodegeeks.com/2011/04/java-generics-quick-tutorial.html

http://www.javacodegeeks.com/2011/04/erlang-vs-java-memory-architecture.html

http://www.javacodegeeks.com/2011/03/glimpse-at-java-7-methodhandle-and-its.html

http://www.javacodegeeks.com/2011/03/dreaded-double-checked-locking-idiom-in.html

http://www.javacodegeeks.com/2011/03/save-money-from-agile-development.html

http://www.javacodegeeks.com/2011/03/design-patterns-in-jdk.html

http://www.javacodegeeks.com/2011/02/performance-anxiety-on-performance.html

http://www.javacodegeeks.com/2011/02/datanucleus-30-vs-hibernate-35.html

http://www.javacodegeeks.com/2011/02/selecting-new-programming-language-to.html

http://www.javacodegeeks.com/2011/02/9-tips-on-surviving-wild-west.html

http://www.javacodegeeks.com/2010/10/android-full-application-tutorial.html

http://www.javacodegeeks.com/2010/12/things-every-programmer-should-know.html

The collection is intended simply to contain multiple and varied perspectives on what it is that contributors to the project feel programmers should know. This can be anything from code-focused advice to culture, from algorithm usage to agile thinking, from implementation know-how to professionalism, from style to substance, etc.In this article we provide a summary of the first 27 "Things Every...

http://www.javacodegeeks.com/2010/05/gwt-2-spring-3-jpa-2-hibernate-35.html

This step by step guide will present how to develop a simple web application using Google's Web Toolkit (GWT) for the rich client and Spring as the back – end, server side framework. The sample web application will provide functionality to make CRUD (Create Retrieve Update Delete) operations to a database. For the data access layer we will use JPA over Hibernate and for a database we will use...