What do you need to know? Java Enterprise Edition. That’s the simple answer.
If you read between the lines what I’m really saying is: “You better make sure you really don’t give a flying toss about technology and don’t care about how frustrating what you spend most of your day doing is.”
A few days ago I was talking with a friend who’s in the process of interviewing with a few big financial institutions in London. The most common questions according to him. Struts, JEE.
Spring was also mentioned by I don’t have much against Spring. If used properly it really does keep your code tidy and avoids duplication.
You see a bank’s idea of a high performance reliable system is a monolithic Java application running a million-billion threads at the same time on a huge machine. Maybe that’s a bit too harsh. Sometimes they do distribute. They just add 15 layers shooting messages at each other in between the 2 they actually need.
Then they wonder why the best talent winds up working for Google, and their budget to deliver 1 application is twice what Facebook spent to build its entire social network.
What I have a problem with is the architects who design these systems. And the clearly-drunken bank managers who hired them.
The most common profile for architects in investment banks (and I met quite a few) is 50-something, stopped following/reading about technology in 1995 and prior to being employed by Mr Mighty WankBank (Thanks City Boy for the name) was VP of over-engineering at the Apache Software Foundation (focused on Struts).
First thing in their TODO list is hire some bright spark straight out of university who has a keen interest in over-engineering and never had to deliver anything in less than a geological era.
That’s when an overpaid team of consultants comes in to “sort-it-out”, at which point the bank loses control over its source-code and none of their developers can understand it any more.
Oh, and then there’s the process, oh the bureaucracy.
Fortunately I also know that in London there are a few sunny spots (techonology-wise) such as Hedge funds who started using Erlang (for example) to distribute their heavy computations over a network.
Now don’t get me wrong I have nothing against JEE per-se. Some of the libraries are actually very useful and improve a developer’s quality of life quite a lot. Just think about JTA.
What is wrong is the way they are used by people who never left the nineties.














I was a huge fan of the original 
