Getting rid of longtime employees might save money immediately, but there's a lot that doesn't show up on a balance sheet. Years of knowing how things actually work can't always be handed over to someone new. Once too many of such people are shown the door, Oracle may discover just how much they were carrying. Saving money today doesn't necessarily mean saving money later.
10 replies (most recent on top)
"except when it comes to replacing you"
what a maroon!
The answer to everything is AI will resolve everything. The goal is AI does everything and minimal human employees. This has been stated by executive level - reality is not found at those high on AI levels.
Experience isn't easy to replace
except when it comes to replacing you
@bn this time around managers were heavily targeted
Management can be reduced with the help of Ai, you need only AI to manage appraisals for 20, employee under one manager, instead they want to keep the managers and fire the employees who actually do the work who actually talk and interact with customers and issues.
While some other companies are still thinking, Oracle is moving fast towards a lean organization with AI agents as engineers. Seniority etc are proven replaceable with the latest models.
With AI it's easy to replace.
For instance, I recently fixed a complicated concurrency production issue in a legacy product and delivered it within a day.
I had 0 prior knowledge on that legacy system, no documentation, every engineer who ever worked on it were laid off long ago. And Codex just needed a codebase and production logs - that's all it took to ingest all codebase and understand workflows and patterns, troubleshoot, fix and test and help with delivery to prod.
With AI knowledge is significantly less valuable. For instance, I recently fixed a complicated concurrency production issue in a legacy product I have never worked with and every single one who ever worked on it before were let go. 0 documentation. The only thing Codex needed a source code and logs - and it ingested the whole system codebase, found and solved issue within a day. And that bug was in a codebase for over a decade.
Until multiple things start really breaking, no one will notice or care.
As long as things continue to get done (even if some take a little longer, and some may not be quite as good as before), that's good enough...
Knowledge and experience is no longer valued. Today's cost is the only criteria that matters. What happens tomorrow will get worked on that when it happens. They will hire someone for less money to solve problems that come up tomorrow. You can look at the problems of a company through different perspectives financial, business, and engineering. They all have different priorities. Right now the financial and business are the most important and the business perspectives are changing from legacy products to new services. If you are in engineering you will be undervalued and frustrated... look for and exit.