The reason I asked this is because I've been in a few software product shop and they all unstable. I guess I'm on the other side of the bridge.
But thank you for the warning though. I should explore further before I make the leap.
lets just go with this -- typically, when a company makes the decision to go with oracle, they've made it for business/marketing reasons, not technical reasons. and this is probably how they're going to make the majority of the rest of their decisions.
No argument between TDD, BDD, DDD, C# vs Java, Linux vs Windows, Commercial vs FOSS and all that crap. Just Oracle, PL/SQL, Forms, and Oracle Financial. There's no Java code at all around there. Pure "module" based. Testing is a lot easier vs to test your own "financial" module written in JEE.
I see it as more practical and suits the business well.
Of course if the business requires infinite customization (in the case of that crazy idea called Business Process Redesign), then maybe hiring a team of software developer is better than buying Oracle.
if you're fine with sitting down and grinding things out, not really solving problems, do what you're told, etc, then, its not bad.
I'm looking at the specific area: financial services (not trading, but more traditional than that: transactions, accounting, etc). I'd love to learn about finances more in conjunction with doing IT related work.