I Retired from PSU, while I worked there in access control and security it wouldn't suprise me if the University had more than that in IT. Their job was to make everything you do harder by locking your work computers down. My wife still works for PSU from home now. If she so much as needs to change printer drivers she has to call IT, wait until someone is available. IT acts like its still 1995 and machines need boot disks with drivers set up. All they really do is make life difficult with their god complex. 2FA would be enough to sign onto work relayed apps but no, the entire machine needs to be controlled because they assume no one even knows how to turn on their machine. Self fulfilling job security, cause problems, solve them, the act like, "see, we're still needed"
When I worked a help desk, nearly all of the "My laptop is dead" calls were power bricks that were not completely plugged in. I'd go so far as to ask people to physically push the ends together to confirm it's plugged in and always get a response that they did. When I eventually go to their desk most of the time I would push the plug in and it would come back. Maybe 10% of the time the battery had physically failed.
Oh I can believe that. There is need for IT stuff. But the bloat should go. No need for an IT department in every single department. Absolutely there are complex routing, data storage and servers. The end user sure isn't able to maintain that. What gets to me the overlap. Every department doesn't need "that IT guy" especially high tech jobs. We maintained access and security devices and servers. And even we had IT guys. We WERE the IT guys. 🤣
If the government had its own fully independent network and operating system that was more limited in what it could do and access than all the stuff everyone else uses, this might not be the same level of issue, either.
1400 is too many either way. A 25,000 person company can easily service itself with under 100 people, and that’s probably still way too high. IRS has 100,000, supposedly, and the job scales fairly well.
It's tax season - I wish Trump would make some sort of statement about whether people should continue to sacrifice their hard-earned cash to this organized crime syndicate or not.
I don't want to pay but really really don't want the consequences of refusing to pay
How many times now have we heard Elon and crew say, “that doesn’t make any sense.”… So great to see the ongoing exposures of outrageous government bureaucratic waste and fraud. I say, take all their computers away and make them write memos to each other on old printer paper. Then fire them.
Having worked in IT for 40+ years, mostly in End User Support, I wasn't as surprised as most at this number. 1400 to service 100,000 end users is a bit high, but not compared to what was the norm even a decade ago. That's roughly 1 per 72 employees. The gigs I did were usually 1 per 100-150 users, but these were lean private sector privately owned companies. You're going to need more bodies depending on how many locations and how far away those locations are from each other. You are also going to need more bodies if there is more than one shift.
While I'm certain much of this is waste, some of it probably is not. Remember - these morons at the IRS still use over 150 COBOL applications, including the mainframe responsible for refunds. It is entirely possible that they need more IT people just to get those laptops ready (and possibly individually recognized by the mainframes).
They also had over 100,000 employees as of the end of FY2024, Fortunately they may lose up to half of them thanks to DOGE findings, and there are recommendations (and offers) from DOGE to modernize their 50+ year old computers - which should cut the number of IT people required to rig the laptops to work with the mainframes.
One of my past gigs was to update more than 1000 WinXP machines to Win10. That included deployment, in-processing the old computers, re-imaging the suitable ones and either prepping the old ones for disposal or building up a boneyard to repair the near obsolete ones where it was worth doing so.
Along the way, I also built a networked imaging system, created and maintained a catalog of the most recent drivers for each system type, built up automated installers that would customize the new system for it's assigned department. On a good day, I could get 20 machines deployed and 14 imaged. Imaging was mostly limited by space and the switch ports I had available on the bench.
When my gig was up, troubleshooting and ticket resolution time had plummeted. If it wasn't a quick fix, it was way faster to just swap the system for a clean one and do a networked re-image of the misbehaving system. Since the imaging was automated, you'd spend about 5 minutes kicking off the service and then it would work on its own. Once you had a replacement candidate, bring the system into the domain and kick off the appropriate installer. About 30 minutes later (and no attention on your part at all), you had a machine ready for the field and that particular job role.
I will say that working on enterprise networks is a PITA. Everything is silo'd and very few folks are allowed significant powers across systems. I had to get the network guy to allow the new PC to work on each port. If the network docs weren't accurate, that was a huge PITA. The DNS guy had to let systems live in their own segmented network for re-imaging and package delivery and give a policy to keep them from automatically dropping out of the domain if they weren't active for a while. The AD guy had to provision a group for systems that were prepped but waiting to be used. At least he let me move them into the right place once deployment was complete. :D
The system was horribly inefficient. Things that were really not that difficult often took a week to get done because you had to grab the attention of so many people. But at least it was extremely secure.
I Retired from PSU, while I worked there in access control and security it wouldn't suprise me if the University had more than that in IT. Their job was to make everything you do harder by locking your work computers down. My wife still works for PSU from home now. If she so much as needs to change printer drivers she has to call IT, wait until someone is available. IT acts like its still 1995 and machines need boot disks with drivers set up. All they really do is make life difficult with their god complex. 2FA would be enough to sign onto work relayed apps but no, the entire machine needs to be controlled because they assume no one even knows how to turn on their machine. Self fulfilling job security, cause problems, solve them, the act like, "see, we're still needed"
When I worked a help desk, nearly all of the "My laptop is dead" calls were power bricks that were not completely plugged in. I'd go so far as to ask people to physically push the ends together to confirm it's plugged in and always get a response that they did. When I eventually go to their desk most of the time I would push the plug in and it would come back. Maybe 10% of the time the battery had physically failed.
So don't overestimate anyone's competence.
Oh I can believe that. There is need for IT stuff. But the bloat should go. No need for an IT department in every single department. Absolutely there are complex routing, data storage and servers. The end user sure isn't able to maintain that. What gets to me the overlap. Every department doesn't need "that IT guy" especially high tech jobs. We maintained access and security devices and servers. And even we had IT guys. We WERE the IT guys. 🤣
Lots of those people are just there taking government money.
The ONLY way the Democrats can keep unemployment rates low is to put people on the government payroll and create USELESS jobs for them!
Right. You sounded like x22
The problem is the bullshit regulations put on “cybersecurity” that do nothing to stop China anyway
These 1400 people are probably swamped maintaining, monitoring, patching, responding to bullshit
This dude makes it seem like government is like AT&T where provisioning is an hour long process and done for 3 years.
Fix the bullshit government regulations that make no sense
Then fix the government bullshit they impose on private sector
I like that idea.
If the government had its own fully independent network and operating system that was more limited in what it could do and access than all the stuff everyone else uses, this might not be the same level of issue, either.
1400 is too many either way. A 25,000 person company can easily service itself with under 100 people, and that’s probably still way too high. IRS has 100,000, supposedly, and the job scales fairly well.
I 2nd that.
Watch Part 2 tonight on Bret Bait's Special Report at 6ET/5CT
Thanks.
It's tax season - I wish Trump would make some sort of statement about whether people should continue to sacrifice their hard-earned cash to this organized crime syndicate or not.
I don't want to pay but really really don't want the consequences of refusing to pay
Pray for it.
How many times now have we heard Elon and crew say, “that doesn’t make any sense.”… So great to see the ongoing exposures of outrageous government bureaucratic waste and fraud. I say, take all their computers away and make them write memos to each other on old printer paper. Then fire them.
Amen.
Having worked in IT for 40+ years, mostly in End User Support, I wasn't as surprised as most at this number. 1400 to service 100,000 end users is a bit high, but not compared to what was the norm even a decade ago. That's roughly 1 per 72 employees. The gigs I did were usually 1 per 100-150 users, but these were lean private sector privately owned companies. You're going to need more bodies depending on how many locations and how far away those locations are from each other. You are also going to need more bodies if there is more than one shift.
Thanks for the information. Good to know.
While I'm certain much of this is waste, some of it probably is not. Remember - these morons at the IRS still use over 150 COBOL applications, including the mainframe responsible for refunds. It is entirely possible that they need more IT people just to get those laptops ready (and possibly individually recognized by the mainframes).
They also had over 100,000 employees as of the end of FY2024, Fortunately they may lose up to half of them thanks to DOGE findings, and there are recommendations (and offers) from DOGE to modernize their 50+ year old computers - which should cut the number of IT people required to rig the laptops to work with the mainframes.
None of this surprises me.
Smart people around here. I see why they retain these people now.
One of my past gigs was to update more than 1000 WinXP machines to Win10. That included deployment, in-processing the old computers, re-imaging the suitable ones and either prepping the old ones for disposal or building up a boneyard to repair the near obsolete ones where it was worth doing so.
Along the way, I also built a networked imaging system, created and maintained a catalog of the most recent drivers for each system type, built up automated installers that would customize the new system for it's assigned department. On a good day, I could get 20 machines deployed and 14 imaged. Imaging was mostly limited by space and the switch ports I had available on the bench.
When my gig was up, troubleshooting and ticket resolution time had plummeted. If it wasn't a quick fix, it was way faster to just swap the system for a clean one and do a networked re-image of the misbehaving system. Since the imaging was automated, you'd spend about 5 minutes kicking off the service and then it would work on its own. Once you had a replacement candidate, bring the system into the domain and kick off the appropriate installer. About 30 minutes later (and no attention on your part at all), you had a machine ready for the field and that particular job role.
I will say that working on enterprise networks is a PITA. Everything is silo'd and very few folks are allowed significant powers across systems. I had to get the network guy to allow the new PC to work on each port. If the network docs weren't accurate, that was a huge PITA. The DNS guy had to let systems live in their own segmented network for re-imaging and package delivery and give a policy to keep them from automatically dropping out of the domain if they weren't active for a while. The AD guy had to provision a group for systems that were prepped but waiting to be used. At least he let me move them into the right place once deployment was complete. :D
The system was horribly inefficient. Things that were really not that difficult often took a week to get done because you had to grab the attention of so many people. But at least it was extremely secure.
It's good to be secure but sometimes, I would like things to move faster. Wish we could do both. LOL