Senior DEVS say that Legacy Code is ruined their morals and is driven to stop collecting alarming rates
- Advertisement -
Related Posts
- Advertisement -
- Outdated technical piles are more than annoying; They drive top developers from the industry
- Developers bind their identity to technical piles, and they stop when they are ashamed of them
- Modern innovation cannot happen when developers are trapped in outdated frameworks and dead -end systems
A growing number of developers reconsider their career due to outdated and inefficient technological piles, claim new research.
A study by Story Blok showed that more than half (58%) of senior developers at medium to large companies reveal that she is considering leaving their job because of “insufficient and” shameful “legacy -tech stacks.”
Among all participants, 86% said that they are ashamed of their current technical stack, with almost fifteen minutes who calls Legacy systems as the most important reason.
Legacy Tech takes a toll on the moral of the developer
Excessive technical debts and dependence on outdated libraries and frameworks also made an important contribution to their dissatisfaction.
Developers take their technical environment personally. An overwhelming 74% said that their technical stack has a “significant” impact on their professional identity, while 19.5% continued and said it actually “defined” them. Only 2.5% reported to feel indifferent.
This deep personal connection can help explain why 73% said they know at least one colleague who has stopped in the past year due to frustrations with their technical stack.
When asked to identify the biggest problems with their current pile, 51% pointed to a lack of core functionality. Another 47% emphasized maintenance challenges, while 31% of concern about limited compatibility with modern innovations such as AI.
Only 14% of the respondents said they should not be ashamed.
The situation is just as disturbing when it comes to content management systems. Outdated CMS platforms were cited as large blockers, with 67.5% of developers said that their current CMS is stopping them from doing their best work.
Almost half described this as a “constant” obstacle, and only 4% thought that their CMS was suitable for the goal.
To maintain developers, employers may have to choose between valuable wage increases or systemic change. The study showed that 92% of developers would require at least a wage increase of 10% to stay in their current role under existing technical conditions, while 42% said they needed an increase of 20%. In the meantime, 15% said they would expect more than 25% bump.
“Outdated technical stacks make your developers unhappy to the point of stopping. Payment increases are a short-term solution … If you want to bring joy back into your development team, you must commit to a modernization route map,” said Alexander Feiglstorfer, CTO and co-founder of Story Blok.
Maybe you like it too
- Advertisement -
