Going the project approach is my usual path. That way I have something I'm interested in accomplishing and that in turn motivates me to learn the technology more. I'm looking at some mobile technologies and will try a couple to see what I like best. I've done Android but I want to look at PhoneGap and see how that plays on iOS and Android.
Reviewing libraries is always good. I recently had a problem with some SQL and found a better way to handle dates and modified a couple indexes. The great thing about SQL is it hasn't changed much over the years. But I'm always learning something new with it whenever I try to do performance improvements on my queries. On Thu, Dec 29, 2011 at 8:02 AM, Thomas Jung < [email protected]> wrote: > Hi Rakesh, > > what a list! Learning stuff is important, but I don't think learning > in a vacuum makes that much sense. Better think of things you cannot > accomplish right now. Where you think you should improve. > > Some reading should be in the mix, but not more than half of the total > time. Good books come with exercises that will take at least as much > time as the actual reading. > > Do something rather than read about doing something. Start a project > or work for a project. Spectacular failure here is better than perfect > learning in theory. > > Thomas > > On Dec 29, 12:22 pm, Rakesh <[email protected]> wrote: > > Hi folks, > > > > I've posted something similar in the past but more orientated towards > > personal productivity using tools and techniques like GTD, etc. > > > > This time I want to get your thoughts on my current (completely > > unrealistic) plan to become a better developer!! > > > > So, I need to learn new things and make sure I know stuff I should > already > > know. I've divided up these areas into the following: > > > > *Existing Java* > > > > - Go through the JCP book, plan to take the exam. Useful for > interviews > > more than day-to-day development. > > > > *New Java* > > > > - Fully review and learn Apache Commons, JODA, Google stuff (like > > collections, guice), concurreny libraries, etc. > > > > *Frameworks* > > > > - Learn Spring 3, Hibernate 4, Cucumber-jvm > > > > *Non Java* > > > > - Oracle, MySQL, Ubuntu > > > > *Languages* > > > > - Groovy, Scala, Clojure, Javascript/CoffeeScript.et al, Ruby > > > > *Books* > > > > - Agile books, Clean coder (loads of others sitting on my Kindle). > > > > *Videos* > > > > - Go through interesting talks on InfoQ, Parleys, TED > > > > My idea for doing this was to dedicate a day of the week to each and > maybe > > 1-2 hours in a session. If I can fit stuff in during my commute (tough as > > its chock full already with podcasts) or at work (maybe 20 mins during > > lunch or stay behind an extra 30 mins) then thats a bonus. > > > > However, I would really like to hear your views, not so much on the > content > > of each, but more of how to manage so many things and deciding whats > > important and how you guys stay up to date. > > > > Cheers > > > > R > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- Robert Casto www.robertcasto.com www.sellerstoolbox.com -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
