If you’re an IT person, make it your mission to get your ORG off Microshit.
lol I wish. I'm a software engineer for a Fortune 100 company; the amount of leverage I have is effectively nil. (Just getting downstream teams to be willing to take our code in Java instead of a godawful proprietary language is a giant fight.) Plus I think the company has some kind of deal with Microsoft, so even the actual IT people probably have no leverage. I make a point of ragging on Microsoft products as much as possible during team meetings though, for what it's worth.
I had to look up what an Open Architecture standard was lol. No, we don't have anything like that. It is indeed internal to the company, but the resistance to moving off of it is due to downstream teams having tens of thousands of lines of it in production that they don't want to re-do. If it's anyone's baby, it'd be a guy who left the company years ago now, so I've instead made it my mission to destroy the last remnants of the language itself from the code we maintain--and luckily for me, so has the boss of our department, so we're making halting steps towards that goal. Unfortunately that means I have to rewrite one of our team's legacy projects, which we know virtually nothing about, in Java in the next 18 months, but it'll ultimately put our team in a much better situation, so it's worth it.
lol I wish. I'm a software engineer for a Fortune 100 company; the amount of leverage I have is effectively nil. (Just getting downstream teams to be willing to take our code in Java instead of a godawful proprietary language is a giant fight.) Plus I think the company has some kind of deal with Microsoft, so even the actual IT people probably have no leverage. I make a point of ragging on Microsoft products as much as possible during team meetings though, for what it's worth.
deleted by creator
I had to look up what an Open Architecture standard was lol. No, we don't have anything like that. It is indeed internal to the company, but the resistance to moving off of it is due to downstream teams having tens of thousands of lines of it in production that they don't want to re-do. If it's anyone's baby, it'd be a guy who left the company years ago now, so I've instead made it my mission to destroy the last remnants of the language itself from the code we maintain--and luckily for me, so has the boss of our department, so we're making halting steps towards that goal. Unfortunately that means I have to rewrite one of our team's legacy projects, which we know virtually nothing about, in Java in the next 18 months, but it'll ultimately put our team in a much better situation, so it's worth it.