universities in the 1980s: writing the majority of internet standard RFCs and their implementations

[cks@mastodon.social]

@wollman @eloy @gnomon The problem confronting the university is that it does not have 10x the money (and it can't get it). If you only have 1x the money and there are 10x the costs, you wind up with 1/10th of what you had and that will probably be disastrous. It will probably be especially disastrous if it comes with the related social attitudes towards service provision and network operation.

[wollman@mastodon.social]

@cks Different pots of money, often enough. I can't speak to Toronto but at MIT the overhead rate on staff is very high compared to the same services provided by an outside contractor. Not ten times as high but enough to be a pretty significant incentive to outsource. That's especially the case if some significant portion of the outsourcing bill can be capitalized (e.g., one-time development and conversion costs).

[lonm@social.vivaldi.net]

@eloy There used to be just a CS / Engineering department. There was no university IT. So it was far easier to make decisions.

Now there has to be a uni-wide IT team, with business goals, compliance, etc, often competing for resources with department specific IT groups. That's not necessarily a problem but makes it much harder to build and deploy new stuff if it always needs approval from higher up.

The worst though is when individual departments IT get folded into to main uni IT, then it's impossible to trial any innovations.

[natex@systerserver.town]

@eloy hey eloy, can i include a screenshot of your post in an article for a culture machine special issue on 'university as infrastructure'?