Yeah, but El Presidente always does that. It's manager psychology- he (well, all of them) can't help being a bit of an 'Evil Dilbert Manager'- so has to tell us we've done bad things occasionally.
Meanwhile at least I'm writing code and not filling the mail system with yet another 'Brunning Information Broadcast' about the latest latest grooviest amazingest new Eclipse plug-in/snap-in/extension module/self-burger-flipping tools ;-)

Oh, and while I'm being paid for my burger-flipping in one of the most common languages in development use, and having to be inventive with Interfaces coz that's all we have and thus getting back to some hardcore basic OO designs, I'm happy. Meanwhile Mr Small-value-of-cool on the other side of the room seems to be cussing a lot at java recently... poor lad, he'll wake up one day and realise it's not just a night mare, he really does have to use 3 classes to open a text file...

If it wasn't for me keeping you up to date, you'd still be using VB6.

Oh, wait, you are...

And I ain't leaping to Java's defence. They *make* me us it. It's not *terrible* - not as bad a RPG, say, or VB. But It's not my *first* choice.

Java is my wife, Python is my mistress. ;-)

I'm using VB6 out of duress matey- the client has no facility to support .net on their Apps Server yet, and won't have during this project's lifecycle, so effectively they're MAKING me use VB6. Gits.

There should be something in the Geneva Convention about that...

Call me "technologically promiscuous" but I have worked in an array of languages including VB, C++, a bit of Java and yes, my forte is the unmentionable language of RPG on the AS/400.

Fact of the matter is, the worse the language, the worse the code, the more the bugs in the end product and the greater the need for companies to pay people like us stupid amounts of money to fix and maintain it....

.....burger flippers turned cowboy programmers keep me employed so no bad language about any "bad" languages from me (If you know what I mean)

;-)