I'm part of a platform team that supports many tenant teams, each with different applications, languages, and package versions. It feels like there's no standardization at all, and while we try to enforce some practices, leadership's approach is often to avoid getting in developers' way. This leads to complicated upgrade processes where we regularly face issues due to outdated libraries or untested apps after we roll out upgrades meant to improve our infrastructure. With our team reduced from seven to just two, we find ourselves overwhelmed and unable to maintain or advance our systems effectively. I'm looking for advice on managing upgrades in such a chaotic environment—how do we break this cycle, or are we just waiting for systems to fail before anyone cares?
5 Answers
It sounds like bandwidth is a huge issue. You need more people to support the growing array of environments. If you can advocate for this, you might also be able to introduce more automated processes or better guardrails around these environments, which could significantly ease your workload.
Honestly, if your leadership doesn’t recognize the importance of a standardized approach for upgrades, it might be time to look for new job opportunities. The team’s size reduction from seven to two is concerning, and without strong tech leadership, it’s tough to advocate for the changes needed.
Consider moving towards containerization to delineate between infrastructure and application management. This way, development teams handle their runtime environments and dependencies, which could free up your team to focus on higher-level platform concerns. It’s a big shift but could improve overall efficiency!
Start by getting clarity on your team’s responsibilities. Ask HR for a job description to pinpoint your official roles. This will help you escalate the issue to management and push for either more resources or a realignment of responsibilities. The chaos you're facing seems mainly due to poor management decisions, so addressing that is key.
One approach is to push for compliance with a technical standards framework. This could help prioritize upgrades, especially when management sees how much money is at stake in terms of compliance. This might mean either increasing your team size or simplifying processes to make audits easier.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures