Let's start !

Hello ! This is my first and only blog.
I'm a java developer since 1999, and a PC enthusiast by the time of Commodore VIC 20.
I managed to see (and use) basic (Vic20, Sinclair QL, early VB), motorola assembler 68000, lisp , Pascal, Turbo C and assembler 386, C++.
Now I'm fond of Java (again and ever more), C++ and Linux, and I'm looking forward to buy a Mac and put inside Linux, VMware and Windows to be really multiplatform (and test).
As a team leader and consultant, I meet many young developers that really don't know why things work the way they do, so they cannot understand what appens when something goes wrong: I'm talking about linkers, mapped I/O, TCP-IP protocol and nowadays the difference between multitasking and multithreading (in a multicore world), and virtual memory and sector and clusters etc...
OK, I feel old and should be if more often than ever I meet colleagues younger than me ...
And it's a good thing young developers want to learn new things like Ruby on Rails etc.. Me too.
But you can't forget the history of IT industry, the good and the bad things done, and learn by studying not only by doing (an excuse of IT manager not to invest and pay for knowledge improvement of his workers, and for developers not to take their job seriously).
My lesson learnt , the one I find leading my actions as a professional is:
know what you're doing, and learn to do it better, the right way (that's why the title for my blog).
I get upset when someone says "it just works, so it is OK".
If I you do something good (or bad) and you don't know why, sooner or later it will explode in your face.
Don't invent the wheel each time, but improve what you previously did.
Reuse your knowledge, and improve it.
Code reuse is less important, but don't re-engineer too often: take a decision and carry on it before changing idea.
You are your best capital.