3 ms·
My thoughts exactly. As is common knowledge, Oracle simply doesn't have any other positions for people with deep knowledge of Java. Once this project was over,
by pje 8y ago
My thoughts exactly. As is common knowledge, Oracle simply doesn't have any other positions for people with deep knowledge of Java. Once this project was over, there just weren't any other options than to fire the whole team.
- pje 8y agoThis is also why the best armies throughout history have always executed their own battalions after every successful battle. Read your history books, people!
- z3t4 8y agoDo you have any references ? Edit: I'm looking for book / article recommendations as I like reading history, and can't believe they executed their own battalions.
- lostlogin 8y agoHigh grade sarcasm detected.
- deleted 8y ago[deleted]
- stefs 8y agosarcasm, i guess - i interpret the statement as: why would you want to keep competent people around, even though their specialties lie in a different area? because competent people are usually also competent when employed in a slightly different sector; the mythical super-programmer is unlikely to depend on a specific language/technology anyway. the comparison wasn't a very good one though: firing your army could lead to soldiers defecting to a possible future enemy, who would then be stronger in an attack. so what does oracle gain by firing a couple of excellent java devs? + no wages paid - they could defect to a rivaling database company: unlikely - bad press: oh well, that's just another drop in the bucket - they lose a couple of experienced engineers that could have excelled in other projects
- seanmcdirmid 8y agoThey might have been looking to downsize anyways, laying off a team that is no longer needed anymore is an easy way to do that, as sucky as it is.