How not to do it.
Game was unplayable with a joystick (digital) . Couldn't even get round the first bend.

The uk are trying to roll out 2Mb broad band for everybody. This sounds like a good thing until you try using the internet on 512kb which almost every building in the uk can receive even those right at the end of a line. It is also perfectly useable for youtube etc. I think this is purely a subsidising scheme for the telecoms company ( cough bt cough ) to upgrade all it's lines. Effectively the users pay for the service and give the company that supply the service the funds to create the service that allows them to charge them at a higher rate whether they need it or not. (Just try getting 512kb broadband in a built up area theses days...possible but I bet you'll end up on a 2Mb package anyway). All a bit useless really if the house owners don't have a laptop / desktop that will work in the next 5 years ( due to vista and xp no doubt not being supported and unable to display the latest .Net advertising schemes that most websites are covered in). So the next great idea? Free laptops for everybody! Paid for by the tax payer!

If I want a laptop and broadband I'll buy one. If somebody is on the dole and can't get a laptop. Help them get a job dont keep giving them free handouts so they can buy a massive telly an xbox a wii and play online so they can sit on thier bum not looking for jobs whilst still getting job seekers allowance.

Sorry just realised I was ranting.

Java is static at compile time. However class files can be chucked around and objects instantiated from them using the reflection classes over networks and across machine types. Kind of like a CORBA implementation that can do the whole spec ( you just have to write most of the code to do it but the functionality exists). I have often wondered if this was the true purpose of the java byte code/JIT method, when those Java desktop boxes appeared I always assumed they would run like a thin client, big database objects on a server, upgradable client applications on the thin client whilst running, no need to stop and start the program. So kinda mega dynamic. Manages to be horrible at the same time.

That is to say let them be brilliant and congratulate them on it, Especially when they've got you out of a tight fix with some rapid coding.
Afterward when the dust has settled get them to go through their code and comment until another member of staff can understand it. Most people quite like explaining to other people how simple/elegant their solution is.
It will encourage them to comment as they code so they spend less time explaining it to other people later, and let them get back to what they do best.
Everyone wins.

I use to work for a small company producing about 30 machines a month. They in themselves were quite complicated bits of kit with many modular components.
Each component would come in through the door. Be Unpacked mounted and wired and the final machine was repacked and sent out.
The amount of packaging we had to dispose of was insane. As an experiment I stored up the amount of packaging for one of our units that we disposed of and compared it to the amount of packaging that we sent out.
What the end user sees land on the door step isn't half of the total packaging in production.