I've been working at my current company for over two years, and I've noticed that our UI is quite outdated—probably around five years old or more. We built it using Angular, and while I've done my best to keep it updated—having upgraded it from version 11 to 19—it's becoming a challenge given its size (over 20 modules) and the number of developers contributing code. The UI not only looks unappealing but tends to be slow and uses excessive memory due to overlapping libraries. I've discussed the idea of creating a new UI with my team leader, but he hasn't prioritized it amid other tasks, citing that if it's working, we should leave it alone. As for our backend, we recently upgraded from Java 8 to 21 and Spring Boot from 2.7 to 3.5, yet we aren't leveraging any of the new features, leading to disorganized, 'spaghetti' code in our microservices. I want to know how I can persuade my team leader to at least have a conversation with our CTO about these necessary upgrades and refactorings, especially as I feel stagnant in my development growth without engaging with modern features.
4 Answers
Definitely consider putting together a proposal that outlines how the costs of doing nothing actually add up. Highlight things like reduced support calls, lower hardware costs due to a smaller memory footprint, and less development time spent on bugs due to better code structure. Bringing hard data to the table can really help demonstrate why refactoring would benefit the company.
I get your frustration! One approach is to frame this issue in terms of business impact. For example, if loading times are slowing down user engagement, that might lead to lost customers. If you can gather data showing that performance issues lead to a percentage of users dropping off before they even get to your features, that could catch their attention. It's all about showing how these upgrades could prevent loss and actually save money in the long run.
You need to gather user stories from various stakeholders, too. Show them what issues they are facing with the current system. Then calculate the net savings—both in terms of time and money—that come with upgrading. Present it all in a clear proposal to your team leader; this is how you can get the buy-in you need.
Make your case like a business analyst would! Build a detailed plan with user stories and the corresponding requirements. Calculate how much the current system costs versus the projected savings of the upgrades. If you can promise stakeholders that their requirements will be easier to meet with an upgraded system while also saving money, you're likely to get their support.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically