[herpienne12]

Thank you for posting this code.

[erkant]

Thanks for providing those stages.

[111027]

Threads are threads, pretty much wherever you go. The dangers are always there, even if concealed from the programmer. I personally prefer writing programs that have a large number or threads(relatively large, mind you) in languages that might seem low level (like C or C++), because the more you see - the more you can anticipate. But when it comes to ease of use with threads, you really can't beat the .NET model. My main beef with .NET threads is when they're broken - they're broken, and you can do nothing to fix them (from what i gather, but a genuine .NET programmer might have better insights).

[Sh4d0ws]

I would have to say I sit firmly in #3, with some slight extensions on working my way into 4. However I think you may want to reconsider some of the placements in #4. Most first and second year courses at my University work with server/client and threading.

[Echo_WarTech]

This truly is a great guide for beginners. I myself am still learning the basic concepts of Java and I found this very helpful. This guide helped point me on what I needed to learn and guided me in an easier direction.

[Magooguli]

If I could I would +2 this string! It is fabulous and I thank you and the various authors of various strings it is related too. Now for the 'I want' part of my post!

Well it is a suggestion really -- what we have here is a basic course in Java - perhaps a couple of suggestions after each level or each block about simple programs to go away and write using the information already presented in this incredible course???

Thanks again!!!

[extremeblueness]

I'm at stage 3:

Data Structures and Collections - pretty good grasp

Advanced Generics - slightly less than data structures, but still pretty good

Graphical User Interfaces (Swing and AWT), as well as Graphics and Graphics2D classes for animations
Event-Driven Programming -learning now

File I/O - check

Exception Handling - check

Database - no idea what this is


Proficiency at maintaining code, including refactoring
Becoming comfortable with a domain-specific third party API. (i.e. something niche, not standard, and possibly poorly designed and a nightmare to work with) - never needed to maintain code yet, but will soon

Finding performance bottlenecks and designing solutions - am horrible at this