3 ms·
At one point I worked with a couple University IT teams. It was a mess. IT little to no control of its own destiny. Basic policies were fought tooth and nail
by duxup 6y ago
At one point I worked with a couple University IT teams. It was a mess. IT little to no control of its own destiny.
Basic policies were fought tooth and nail by departments and influential professors / individuals who themselves didn't understand the ramifications of their decisions.
IT budgets would get cut and monies given to departments who would build catastrophes of networks, and when the department was tired of it would get handed to IT to make it work, the entire budget already having already been spent on making a mess.
I worked on several projects where complex microscopes or millions of dollars of equipment were connected to off the shelf consumer networking gear (and then they'd blast it with gigs upon gigs of data in a few milliseconds) because the consumer networking gear is what the folks in that department knew how to use. It was then handed to the IT team and then tickets opened about how 'it doesn't work' / it is described as an IT failure when nothing works.
- JeremyNT 6y agoThis exactly matches my own experience. I work in University IT as a developer in the central IT department, but I started off in one of those "shadow IT" groups. There are little islands of technologists embedded with grad students who continue to make many things run on shoestring budgets and with minimal oversight from IT professionals. I've seen things change in recent years, though. The central IT department is gradually gaining traction in some of these places. That isn't a panacea, of course, because we have our own issues. But I do think overall the availability of senior IT staff and programmers is a huge boon for these small teams who are starting from little to no experience in the field.