August 11, 2015 at 9:05 am
I have spent most of my career dedicated to medium sized systems on a single platform with customization for different clients. I now find myself in a County Govt with about 2,000 employees with 100 small to medium systems across all VB versions from VB6 to VB2012 and their related Crystal, as well as SSRS, SQL from 2005 to 2012, a little Java, some variety of desktop OS, etc. And I'm not mentioning 3rd party software. I personally am the go-to person for 25 of these systems. I'm wondering about strategies people have adopted for environments like this (other than quitting).
If this is too broad of a question, help me narrow it down with your questions.
August 11, 2015 at 6:04 pm
Personally, I'd study the environment and find all the shortcomings and dangers in the environments. Then, make a plan to homogenize the environment a bit along with an explanation of the ROI of doing so and get management buy-in. Otherwise, I'd just get used to it.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 12, 2015 at 7:01 am
I'm going to read into that answer a little and say that I hear you already recognize some shortcomings. ROI on upgrades is a bit difficult to calculate, especially due to the differences between upgrading from say VB6 to VB2003 (very difficult) and VB2005 to VB2012 (easy). The pains experienced years ago tend to linger, despite any new data. Also, published estimates of upgrades have always been useless in my opinion, so it's more about developing trust between the team and management, which is a different topic.
So, I'm really looking for strategies, other than resigning to it, but if others think the obvious answer is "just upgrade", then I'd be glad to hear that too.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply