3 ms·
Corporate users need to seriously rethink their glacial technology adoption cycle. In the BigCos I've worked at in the past, we're usually told it's due to secu
by bane 15y ago
Corporate users need to seriously rethink their glacial technology adoption cycle. In the BigCos I've worked at in the past, we're usually told it's due to security, yet we're almost always stuck on versions with glaring security holes that were solved years ago.
The problem indicated in the blog post (and the comments) is that the software ecosystem, add-ons, various vendor web sites, etc., take too long to bring up to speed. I can also attest to this, I worked at one organization that was stuck on IE 6 because the bloated and ridiculous expense reporting system wouldn't work on anything newer. They finally had to upgrade to some newer version because a major customer site simply refused to work with IE6 and we couldn't turn in our work. The weeping and whining from the corp IT department over having to upgrade the enterprise lasted for a year at least. It was actually a major contributor to me leaving the company I found it so absurd and annoying.
Strange that the vast vast majority of web sites on the open web don't seem to have a problem with this. Could it be because they write to standards? I always wondered what bizarre things were going on in that old expense system that just broke on new browsers.
- dexen 15y ago> Strange that the vast vast majority of web sites on the open web don't seem to have a problem with this. Could it be because they write to standards? I believe ther's a better answer: the owners/operators of the websites are incentivized to update them to current popular browsers. Let's face it, writing to standards helps, but does not guarantee good cross-browser compatibility if the website is somewhat complex. Also the owners/operator usually are themselves -- or have on hand -- the people that can modify the site's code right away. May have something to do with popular sites being either very simple, or being developed all the time. To contrast, the corporate IT is the embodiment of ``don't touch it if itsn't broken'' and ``fill in those three forms before you check any new code in'' mindset. Os just outright procurement of huge systems from external vendors with no contractual provisions for updates to match current software. (which was one of the ills of my previous workplace, sigh)
- bane 15y agoTo contrast, the corporate IT is the embodiment of ``don't touch it if itsn't broken'' and ``fill in those three forms before you check any new code in'' mindset. I agree 100% with this and I think that this is the mindset that needs to change. Back in college I took a course in Enterprise Architecture where this mindset was ingrained as good practice. I finished the class thinking that this was all terribly terribly wrong headed.
- kenjackson 15y agoCorporate users need to seriously rethink their glacial technology adoption cycle. In the BigCos I've worked at in the past, we're usually told it's due to security, That's not the main reason (security). It's usually getting stuff working at all given the sheer size. There was a Fortune 100 company I was consulting at and they had more "important" LOB apps than they had employees. And this was a big company. The sheer amount of code they had internally would dwarf the amount of code that MS ships. They build this code against a given browser (although a lot of it isn't browser based, but for the sake of this discussion). They can't just take a new browser and break half (or even 10%) of their apps. At the same time, it will take a year or two to get their apps all working. And these transitions do happen, but they're multiyear affairs. And in particular the one I worked on got 15 year support guarantees from a couple of companies before they moved forward -- they don't want to do this effort every six weeks. They want to do it once, and be able to stay on it 6-10 years (if not longer). Strange that the vast vast majority of web sites on the open web don't seem to have a problem with this. Again, for major companies 75% of their apps or even 90% working isn't sufficient. Today 100% of our apps work -- tomorrow 100% better also work.
- bane 15y agoAnd these transitions do happen, but they're multiyear affairs. And in particular the one I worked on got 15 year support guarantees from a couple of companies before they moved forward -- they don't want to do this effort every six weeks. They want to do it once, and be able to stay on it 6-10 years (if not longer) I agree that this is how corporations operate. The reasoning is that IT is thought of as a necessary evil, "lets just get it over with". But this mindset has to change, just like a company wouldn't let their physical buildings fall apart, corporate IT systems need a proper maintenance mindset. Why write to a browser? Everybody knows this is dumbheaded. Write to "browsers" and put in place a plan to keep the web-based software up-to-date with modern standards. It costs way more to build a new system, migrate over (in a multi-year migration process), then tear down the old system then to just keep your crap up-to-date with a maintenance staff. It's akin to building a new office building after 5-6 years and moving everybody around, then tearing down the old building, because the county put a mandatory recycling program in place and the corporate trash policy didn't know what to do with the recycle bins. As a result the old office just filled up with glass bottles and aluminum cans...so they had to move to an empty office building...for the space.