- Obsolete technological batteries are more than boring; They lead the best developers in the industry
- The developers bind their identity with technological batteries, and they leave when they feel embarrassed by them
- Modern innovation cannot occur when developers are trapped in obsolete frames and endless systems
An increasing number of developers are rethinking their careers due to obsolete and ineffective technological batteries, new research said.
A Storyblok survey revealed that more than half (58%) of senior developers reveal averages to large companies plan to leave their jobs due to “inadequate and embarrassing technological batteries”.
Among all the participants, 86% said they feel embarrassed by their current technological battery, with almost a quarter citing systems inherited as the main reason.
Legacy Tech has consequences on the morale of the developer
Excessive technical debt and dependence on libraries and obsolete executives have also contributed to their dissatisfaction.
Developers personally take their technological environment. An overwhelming 74% said that their technological battery had a “significant” impact on their professional identity, while 19.5% went further, claiming that it “defined” them. Only 2.5% said they felt indifferent.
This deep personal connection can help explain why 73% said they knew at least one colleague who left last year due to frustrations with their technological battery.
When asked to identify the biggest problems with their current battery, 51% highlighted a lack of basic functionality. Another 47% highlighted maintenance challenges, while 31% expressed concern about limited compatibility with modern innovations such as AI.
Only 14% of respondents said they had nothing to hinder.
The situation is also disturbing with regard to content management systems. Obsolete CMS platforms have been cited as major blockers, with 67.5% of developers saying that their current CMS prevents them from doing their best.
Almost half described it as a “constant” obstacle, and only 4% estimated that their CMS was suitable for the objective.
To keep developers, employers may have to choose between costly salary increases or systemic changes. The survey revealed that 92% of developers would require at least a salary increase of 10% to stay in their current role in existing technological conditions, while 42% said they would need a 20% increase. Meanwhile, 15% said they would expect more than one bump of 25%.
“Obsolete technological batteries make your developers dissatisfied with the point of smoking. Payable increases are a short-term solution … If you want to bring joy to your development team, you have to engage in a modernization roadmap,” said Alexander Feiglstorfer, CTO and co-founder of Storyblok.
