Practice,practice,practice..Practice what?

What I would do is practice on a "fake" service... all software should be seen as a service, not necissarily as software... (in my mind, at least)... the application is fetching something, freeing up resources, and then allowing the user to do what it wants to the chunk of data it requested, then cramming it back into whatever db it plucked it from... all of this should be done asyncronously and without affecting the UI, you cant have your UI waiting to draw the screen while the application goes and fetches a web service, so you have to thread that seperately... then maybe the two threads have to communicate, and possibly update the UI.... aloso, there could be multiple Forms open that need to communicate... or multiple threads, and thread pools... I know I'm focusing a lot on threads, but I think it's an essential part of C# programming, enough so that people should really be threading things that take more than a split second to do. the whole idea of the "fake" service is that you start developing software based on real world needs, becauser really, nobody needs software that keeps calculating PI in the background! ;) goodluck.