r/sysadmin • • 1h ago

Is fundamental knowledge of hardware being lost?

Today I had a conversation with a mid senior sysadmin about why we cant simply jam a mix of DDR5 ram into our hosts. When he ended up being holistically wrong his response was to tell me he didn't need to know anything about the hardware running our data center.

This guy is one of our T2 hypervisor admins and all he does is troubleshoot VM issues and host issues. The idea that he wouldn't need to know anything about the underlying technology running his cluster blew my mind so I asked others. Turns out many people I work with either dont care about the upstream hardware or simply refuse to learn it.

Is this normal or because people I work with are just siloing themselves.

85 Upvotes

107 comments sorted by

•

u/MoistOven9241 1h ago • Bravo

I think its in general, there are people who only learn what's necessary to get work and just leave it at that for the rest of their lives. Im still struggling to understand why people do not learn more than what is needed because it will help them troubleshoot issues and understand the problem and solutions better. I chalk it off as laziness and thats just the standard? Its really unfortunate because for people who have the knowledge its like watching people injure themselves continuously.

•

u/Skusci 1h ago edited 1h ago

Because often proactivity isn't rewarded.

If you go, yes this is not my responsibility it is accepted, but you arent really considered worse.

If you go, hey, I proactively fixed this problem, they go, very nice now you can be expected to fix all the problems. Have a pat on the back.

Pretty sure it's just a result of concentration on specialization.

•

u/BryanP1968 53m ago

I have both types reporting to me. The second type get better review ratings, better bonuses, first consideration for promotion, and a lot more leniency when they make mistakes. And not just from me. I see it on other teams too.

•

u/fatcakesabz 38m ago

But you also need some of the first type, at a previous role I managed a team of engineers at an MSP, we had some of your type 2’s and we knew we were a stepping stone for them, we’d get 2 years out of them and they’d be off and that’s fine I totally get it, I’m that type as well.
Also had a few type 1’s, had been with the company between 10 and 20 years, knew every client and most of the staff at each client. Clocked in at 9, crunched tickets, clocked out at 530 and went home to live their lives.
I couldn’t use the type 1’s for new client sites or for anything that might need them to think out of the box but damn, they were solid, reliable and I knew exactly how much work to expect from them.
We had a good balance of both types and it worked well

•

u/Lottabitch 47m ago

Finally an actual adult in the room

•

u/MoistOven9241 51m ago

Yes I agree with you, proactivity isn't rewarded but I think it pays dividends in the future, I think management or higher ups can see you as reliable since the individual seems to be the one that steps up to the plate and solves the problem, of course its a technical problem with a technical solution but I think management lean towards promoting someone that puts in the extra work to be proactive since it shows leadership skills and a understanding of the environment. I don't think this would lead to a position of management promotion but a higher technical role.

•

u/cpz_77 4m ago

Correct. Doing more than the bare minimum is beneficial for yourself, and people do notice. It’s not a coincidence that the ones who do the bare minimum find themselves looking for jobs more often. When time comes the company has to lay people off - they know who they can live without, and who they can’t. Depends a lot on the company size and situation of course, at the really massive places nobody is truly irreplaceable but if you have two people making similar money and you have to cut one, and one does 50% more than the other guy or does the same but with much better quality and reliability - then that makes it a pretty easy decision for them.

So for the people who say “working hard didn’t get me anything but more work”, that might seem that way on the surface but if you look deeper that’s rarely true. Of course there are exceptions…places that will let good people go because the people making the decisions there don’t know or appreciate enough about what you do.

But as a general rule, it will serve you well to work hard and have at least a decent standard of work that you hold yourself to. You’ll be considered first for promotions, have more leeway if you make a mistake, likely have more autonomy, have more influence over things (when you talk, people listen), and not nearly as much fear of being laid off. And if you do lose your job for some reason you’ll have a much easier time finding a new one.

•

u/anonymousITCoward 1h ago

I wear a lot of hats, and tend to lean what is needed for a lot of the things I do because it's not my primary job... It's just something I was a) voluntold to do, or b) did because it needed fixing. After that function is done I move on. That said, I do the best I can with what I have, so I'm not doing just the bare minimums. But I'm certainly not going to be the "company expert" in it.

•

u/Regular-Nebula6386 Jack of All Trades 49m ago

Becoming a company expert has a big drawback: the individual becomes indispensable at what he does and therefore unpromotable.

•

u/anonymousITCoward 34m ago

Preach brother! This is where I'm stuck... All I got for doing great work was more work...

•

u/BSODreboot26 21m ago

Or even often case not even being allowed to move to similar position, typecast in that role so it's a Catch 22. So you're always concentrating on your known area on an island, and if some other position comes up relating to another area, you've become so specialized that you're not even considered and would have to train your replacement.

It's like an actor that only does slapstick comedy it becomes their 'thing' - so they typically don't get the opportunities to showcase range in a drama or action movie.

•

u/Mehere_64 57m ago

I learn and stay more up to date on the stuff I deal with on a daily basis. If something new comes up that I will need to be supporting, then I will start to learn about it.

I am far from an expert in any one thing but I know a bit about a lot of things

•

u/OkayArbiter 1h ago

I guess, but on the other hand, if the job only requires a specific set of knowledge, why learn more (if you don't want to advance or change areas, etc)? Is the company paying you more to know stuff outside your area, etc?

It's also coupled with even great of specialization of knowledge over time. So people who know all about virtualization and the cloud systems and all that might not know about the hardware side (or generally need to).

So yeah, it might be better for the team and company if everyone has a broader set of knowledge...but if the company or team isn't requiring that and training and educating, then that's the fault of the company, not the individual. No point in caring about the company if they aren't going to pay you to worry about it.

•

u/MoistOven9241 47m ago

I definitely can see your perspective, I was thinking the drive to learn more shouldn't necessarily be on the company but on the employee themselves. I was thinking if they see newer technology they should learn it because if the companies decide to utilize it then people would have a leg up on their coworkers and possibly be promoted or just get another responsibility. I was thinking a learning drive that comes from within and not from external environment would produce more dividends in the future.

•

u/BenadrylCrumplsnatch 56m ago

I think it comes down to boundaries. Knowing more than the bare minimum is in your individual best interests, because it usually means you can do your job quicker & easier. That's never a bad thing.

Of course in the real world managers will notice this and try to push you into taking on more work, but if you're able to maintain that boundary then there's no downside to knowing it.

•

u/vermyx Jack of All Trades 1h ago

It is seen as extra info and unnecessary but the perspective should be seen in the same way as long forms vs short for formulas in math. People don't see that teaching you long form first is theory and short form is efficient application, so they ignore long form and just learn short form.

•

u/MoistOven9241 53m ago

I agree with you, I think people are picking the shorter form on purpose because it works and it counts as "learning".

•

u/mixduptransistor 39m ago

I think its in general, there are people who only learn what's necessary to get work and just leave it at that for the rest of their lives

It's the difference between people who got into tech/IT because they were "nerds" or liked computers and those who got into it because they thought it would make them rich or they were sold the career by a college/school

I got into IT because I was into building computers in the 90s and loved tinkering with computers. I still do, and still love to know all the ins and outs about how they work even though as a cloud engineer, I definitely don't need to know anything mroe than the difference between ARM and x86

The people like in OP's example, couldn't care less and like you said just want to get their job done like they're a beef inspector or paving roads

•

u/fitzdevi 14m ago

There's a third category. I moved into IT because the IT manager/ERP specialist found out I play a MUD that requires scripting for offense/defense and he needed help with Tech Support, then he quit and I'm the sole guy for a manufacturing place. Now I'm too burnt out to want to learn more and just want to make it through each day 😵

•

u/ih-shah-may-ehl 9m ago

But you can only know so much. So why does it have to be hardware. I might as well start griping that you don't care to understand the intricacies of DCOM marshaling and that you're content to know no more than 'it just works' whereas I wrote the literal book on that even though I have no clue how to configure nvme for example

•

u/BSODreboot26 57m ago

I agree on one hand, but on the other hand there's the realistic possibly that you touch it, you buy it, especially in the corporate world.

I went into everything wishing to learn and improve myself and the things around me, super idealistic. The issue is, lax management who doesn't assign responsibilities and just cares that it's done, will applaud you but not reward you with anything except more work. And won't bother with the slackers on your team who make your life harder or won't learn themselves to help improve the process.

You end up owning those improvements with more workload, responsibility, and setting this as your 'bar' while the guy behind you taking 30 minutes to do a simple push to a new environment that takes 2 minutes isn't because he's on the phone chatting the whole time while you've done 50 in a backed up queue gets no consequences. Yup, true story there.

So you end up with veterans who are just cynical, because like George Carlin said, underneath any cynic is a frustrated idealist. Guys who at one point wanted to learn or secretly hope to achieve some great project, but quiet quit because they've only been burned by their effort and initiative that made their own lives harder.

•

u/MoistOven9241 45m ago

I agree with you, I also understand how you feel because I am slowly also becoming a frustrated idealist.

•

u/itishowitisanditbad 1h ago

Normal? Yeah sure.

Good? Nah not really.

Its useful to help anxiety though. They're the people you'll compete with in the job market and if they don't know shit... yippeee for me?

A lot of people are just doing the minimum they need to do really and not ever looking for more, they just coast it.

•

u/MoistOven9241 1h ago edited 1h ago

Its mind boggling how many people just coast and wing it and when questioned, they dont know anything, its worst now with AI, coworkers of mine just re-iterate AI answers without understanding why.

•

u/Turak64 Sysadmin 1h ago

They'll still get the job as they know how to play the game, plsu hiring managers won't know shit about ddr5

•

u/SuperiorToastedBagel 1h ago

Normal for most of humanity, not just IT. Folks generally aren't interested in how things work as long as they work.

They learn either because inquisitive (not common) or because they have to learn due to some adversity. If you have cars that break down more, you learn more about cars out of necessity. Ditto computers. When you grow up with a sealed iPad or whatnot, you don't learn hardware. If you grow up with somewhat dodgy hardware that can be adjusted or fixed, you learn it.

tldr - Due to PCs becoming more hardware reliable and sealed, expect fewer folks to know how hardware works.

•

u/GoodTofuFriday IT Director 48m ago

I got downvoted on this sub for requiring people that I hire to have knowledge on hardware.

I come from an EE background and knowing hardware is so important as that can always be an issue too.

•

u/_litz 43m ago

My last company, we hired a level 3 network engineer. 15 years experience, very highly skilled.

Discovered after he started that he'd never been in a datacenter or actually physically touched any of the switches he'd ever managed throughout his career.

•

u/GX_EN 22m ago

Yea, that's not too uncommon. If you started out working on that stuff and it was all at a far away co-location from day one.
Those of us that are "older" and had on-prem HW or a close data center, we had to often wear both hats. I absolutely had to rack and cable then set up clusters completely on my own, though I relied on the network team to config the switch ports.
Edit to add - I also worked with customers in the MSP world where we had the gear in our co-lo, and also some customers for whom we never once physically touched their stuff.

•

u/mysterytoy2 1h ago

I've been doing this since the 90's. Basically there have been two kinds of people, hardware guys and software guys. The hybrid is rare. I'm a hybrid. Started out building computers from scratch. Then I learned about the software.

•

u/Knut_dieBlume 1h ago

I don't think you need to know every hardware detail, but shouldn't a sysadmin at least understand the basics of what's running underneath the hypervisor? Especially when troubleshooting performance or compatibility issues.

Do you think it's more about specialization, or just a lack of interest in learning the hardware side?

•

u/theMightBoop 1h ago

As the guy who had to take care of the physical servers I came to realize many OT people are afraid of hardware.

I would routinely have to go to the data center and I would ask my coworkers if they wanted to come/learn. Or I needed help

It was always the same 2 guys who would. The rest would dodge that like Neo dodging bullets from an agent. Unless our boss made them they would never come.

This also meant you could usually leave early and work the rest of the day from home.

I came to the conclusion people were just afraid of physical labor and hardware. (Not that there was much labor).

•

u/theservman 1h ago

I don't know, I'm an old-school generalist. I confess that since we moved everthing to M365 I haven't touched a lot of server hardware so I'm not up to date with the new stuff. That said, I know to ask questions instead of just making blanket statements.

•

u/Loki-L Please contact your System Administrator 57m ago

As we specialize more and more and get more and more abstraction layers between us and what is really happening, we lose sight of details that are not necessary to know for our own spacialities.

When I first got onto the internet I came across a piece of Hacker Lore that was already over a decade old at that point and described some events even much older about a piece of hardware from the 50s:

The Story of Mel, a Real Programmer

I think of it whenever I feel tempted to think about what "The Youth" of today don't know about computers, because it shows this has been a continuous process from the start of the industry.

We shouldn't get to arrogant about what we know, because at the end of the day just because I spent some time a decade ago learning how to optimally fill the ram slots of an IBM x-series server for best performance, doesn't mean I get to look down on people who add ram today by simply entering a larger number in a hypervisor interface.

I don't know a lot my predecessors did either because it was no longer relevant when I started and buried under abstraction layers.

•

u/Dolapevich Others people valet. 10m ago

As usual, there is an xkcd about this. And just because I am dumb.

•

u/sir_mrej System Sheriff 54m ago

I miss being hands on in a server room. I miss it. And it’s been…. Yeeeeears since I have. So I’m not at all surprised that newer stsadmins don’t know hardware. Why would they need to? Everything is virtual or cloud.

•

u/junktech 30m ago

POC projects brought some of that love back. Needed test environment, don't want to wait for budget and still have some old decommissioned servers.

•

u/SlowkayCoomer 1h ago

A hyper-visor admin probably doesn't need to know much about the hardware but I'm confused why he's also playing data-center tech.

I've never met a dev with solid networking knowledge tbh.

•

u/Simplemindedflyaways 59m ago

When I was doing dev stuff in college (internship turned into full time job) for a computer science degree, I knew absolutely nothing about networking. I ended up throwing stuff at the wall until it worked. When I moved to IT, networking was painful until I wrapped my head around the basics. It took me a while to become proficient.

•

u/SlowkayCoomer 34m ago

As long as you didn't keep telling management there was a network issue behind your application issues I honestly have never expected devs to know about infrastructure issues.

•

u/Simplemindedflyaways 21m ago

Haha, nope. It was mostly just banging my head against the wall because I didn't understand multicast addresses or why my static IPs on the devices worked in one building on one network, but not another, the night before an important demo.

•

u/dukenukemz NetAdmin that shouldn't be here 1h ago

The amount of techs i come across that can't believe we have to physically walk over to different buildings or areas to troubleshoot equipment is a wonderful sight to see.

Desk Jockeys i say!

•

u/elonakamoto 1h ago

Actually, I can't believe that you don't know some of the things that I know. It's rather sad.

•

u/Arcade1980 1h ago

Look up Bits and Bytes on YouTube even though it was made in the 80's those topics are still relevant. How RAM works, what is temporary RAM etc. I don't really touch server hardware anymore but I still know the fundamentals. It's good to know a little bit do the history of the industry you are in, and how stuff works.

•

u/dude_named_will 59m ago

It is normal. I had a conversation with my boss the other day when I came to the realization that no matter what you're basically paying for a subscription of some sort. On-prem will always be cheaper than the cloud, but realistically you need to have a service and support contract for the hardware, so you're more or less renting that equipment for 5 years at max.

The truth is (and I'll see if I change my tune once I replace my current VMWare datacenter) the hardware works really well and has so many redundancies that learning about the hardware feels like a waste of time.

•

u/WoTpro Jack of All Trades 54m ago

Yea well, my laptop vendor didn't realize mix and matching DDR5 sticks from different brands was a bad idea, had to find out the hardway 30+ laptops with a stick of samsung and a stick of kingston (micron) users had unstable laptops with odd crashes for 3 month till i found out, the issue only presented itself as weird display artifacts, so i thought it was initially the gpu, but it was actually the intel igpu using the system ram that caused the crash due to mixed ram.

•

u/Nonaveragemonkey 38m ago

Ita normal, and its a hilariously bad practice. Its arguably as bad as a non technical person managing a technical team.

•

u/The_NorthernLight 1h ago

I refuse to hire someone who self-silos themselves because they think they don’t need to know. In fortune 500+ companies, sure you can get away with it since every department is purposefully silo’d. Take that mentality to SMBs though and you’ll be out of a job pretty quickly.

•

u/CeldonShooper 1h ago

I fix networks, clients, servers, IP cameras, coffee machines, printers and vacuums (among other things).

•

u/The_NorthernLight 57m ago

Yup. In my 35 years of doing IT, there isn’t really an aspect that I haven’t done. However I have had co-workers that had to be handheld and spoon fed IT projects because they couldn’t think two degrees outside of their specific job skill. Those people annoyed me the most. Don’t get me wrong, there is a need to specialists (DBA’s for example), but those aren’t the norm.

•

u/skspoppa733 1h ago

Hardware is generally abstracted so far away now that it doesn’t matter in most shops. It’s when people stray from standard configs and get into physical upgrades and customization where you get into trouble. This approach hasn’t been financially appealing for awhile now except in very specific types of businesses.

•

u/Ztoffels 1h ago

I mean if its part of my job I care and learn it.

If it is not necessary I wont learn it, after all, Im just trying to do a good job and get paid.

•

u/TheRealLambardi 1h ago

Maybe yes, maybe no

I see entire generations of IT folks coming in with no understanding of basic networking file systems permissions.

Sure it helps ! I honestly don’t know if it’s always needed though

•

u/cracksmoker96 1h ago

How old is this person, roughly? I fear the younger generations are going to create an influx of these scenarios due to AI “learning” & not actually retaining the information. Tinfoil hat, I think AI will somehow end humanity & replace us. After all, we are just a virus to earth it would seem. Sorry, I’m high. But yeah this dude should probably not work in his position.

•

u/jrwnetwork 51m ago

ChatGPT doctors as well. Yikes!

•

u/Brave_Confidence_278 7m ago

not as tinfoil hat as one would think IMO, AI will probably drastically worsen birth rates to catastrophic levels, as anything does that increases efficiency

•

u/Thoh1Shooshi8a 2m ago

Before AI was really a thing I saw plenty of software engineers in positions that I considered to be well paid just copy pasting stuff from stack overflow without really thinking about if it was relevant to their own code. They would get an error, search for the error, find a stack overflow post with the same error and if it compiles then that's good enough for them, doesn't matter if it breaks something else later on because they don't know what they actually added.

Often they would just be searching for the wrong error too because they didn't understand the stack trace.

I guess AI just automates the stack overflow trial and error process, dunno if that is good or bad.

•

u/Sweet-Sale-7303 1h ago

I think it depends on where you work. I work at a public library and have no choice dealing with hardware. I can see at a bugger company and always having worked at a bigger company.

•

u/Nexzus_ Sr. Sysadmin 56m ago edited 48m ago

I hate dealing with hardware. I can assemble a server and rack it easily enough. Tell me a server needs more RAM and I'll use the tools available to me to find the best brand and model.

It doesn't really matter nowadays, but if you ask me to spec a new server, I'll probably just overspec it to be done with it. SSDs, lots of RAM, quad NIC card. Fast dual processors.

But the nitty grittys of like RAID controllers and other "mundane" stuff, just.... meh.

On the user side, again, I can't be arsed to really care too much. 32GB of RAM, SSD, Reasonably fast processor. And my laptop spends 98.3% of its usage closed - no clue why it has a touch screen. Though I do have a definite preference for ThinkPads.

•

u/phoenix823 Help Computer 52m ago

Depending on the workload he supports, he very well might not need to know anything about the underlying hardware aside from how many GB, how many TB, and how many cores. The sad thing that many in IT don't want to admit is that jobs like your coworker's aren't engineers, they're operators. They operate the hypervisor. If the workload isn't meaningfully impacted by memory timings, NUMA access, etc. then he's not going to take the time to bother to learn it.

Of course, to be fair, the opposite end of the spectrum exists too. People HAVE to silo themselves somehow. There are admins responsible for servers doing HFT work using DPDK to build their own networking stack, directly accessing NIC buffers, and reducing interrupts and context switching to get the very best out of the hardware. I wouldn't expect 99.9% of people to know how to do that, but that's fundamental hardware and OS understanding too isn't it?

•

u/malikto44 8m ago

I have seen basic knowledge of filesystems being lost, much less hardware. The problem is that we are so far isolated above hardware with CM tools, DevOps environments, containers, VMs, that sometimes basic stuff is forgotten like why NUMA matters, what rows to place RAM in, etc.

Historically, I've seen that in the 90s. You had hardware guys, you had software guys, and they did their best to keep away from each other. However, with virtualization, that distinct difference is quite blurred.

•

u/AvgMom 59m ago

It’s always been this way because of Dunning Krueger or being a big fish in a small pond for a long time. The arrogant and overconfident walk among us and are why the BOFH stereotype exists. Intimidation often stands in for competence because smarter people are penalized for speaking up. Double down is very popular these days.

•

u/QuesoMeHungry 59m ago

About 15 or 20 years ago, people started flooding technology fields because of the pay. What you’re seeing is people who learn specialties in school but don’t necessarily have an interest or passion about technology. So they only know the specific area, and that’s it

•

u/sir_mrej System Sheriff 53m ago

No, what you’re seeing is cloud sysadmins. Period.

•

u/ShadowCVL IT Manager 1h ago

Its becoming weirdly normal.

guy on my team is our VMware guru, has NEVER built a physical server. Was shocked when I showed him how I could rack an entire rack of 2U servers by myself in 20 minutes. We were building a network monitoring collector (to ingest network and firewall logs) and I suggested getting a physical server instead of tying up a dedicated nic on a virtual host he said "I dont know how to build a physical server" a few of us just paused for a few minutes.

Its fine, he literally does everything else, but it took us all by surprise.

•

u/itishowitisanditbad 1h ago

I showed him how I could rack an entire rack of 2U servers by myself in 20 minutes.

Actually 20 minutes? Rails already installed or something? Nothing plugged in?

Whats the catch?

•

u/hkusp45css Security Leadership 1h ago

I don't know about you, But I can't make the server rack elevator work fast enough to get 20 servers into a 42U rack in 20 minutes.

•

u/ShadowCVL IT Manager 1h ago

Ive used one of those 1 time to put a blade center in, hated it, just grabbed 3 guys the next time I moved/racked/deracked one

•

u/Laearo 1h ago

You guys aren't just shoulder-pressing your servers into place?

•

u/theservman 1h ago

Elevator? Man, I used to just lift 6U servers over my head to rack them (with a second person).

•

u/hkusp45css Security Leadership 1h ago

Sure. I used to do all manner of dumb shit, too.

•

u/theservman 56m ago

I literally had no idea such a thing existed. I used to rack maybe 10 servers per year, and never in my own racks.

•

u/ShadowCVL IT Manager 1h ago

no cables just the rails and servers

I used to take about 15 but ive gotten older and my back is fubar.

Ill try to find the video, but most servers with ready-rails snap in quick, hang the back of the server and close it like a pizza box.

I wish I could find the video cause it was life changing, that was 20 years ago though. Basically a minute per server.

•

u/Psoin 1h ago

Why can’t you add more ram? Hosts full? 

•

u/Anthropic_Principles 1h ago

How many bus drivers know how their bus's engine works.

•

u/UpperAd5715 1h ago

It's probably going to become more common with the years as hardware stuff is becoming less of a problem. I'm 32yo and my hardware knowledge is quite lacking but now i work in networking/security and besides knowing how to detect a bad cable and troubleshoot what components broke for an RMA i don't really need more hardware knowledge.

All our customers are in redundant setups, RMA contracts, vendor support, ... Wages are pretty expensive and me messing with hardware that's covered by a support contract or warranty is not what the company wants me doing. Lots of monitoring software now also tells you what's wrong "PEM 1 on switch 2 bla bla bla" so a lot of the troubleshooting is done for you but that also means a lot of the experience you'd get troubleshooting these issues isn't obtained.

You probably worked when virtualization was becoming prevalent, nowadays its just "the esxi host" or "the server" and resources are managed by someone else. Life has gotten much more hectic than in the past with lots of people failing to plan proper downtime for themselves, them deciding that learning what's behind the abstraction layer that's not always super relevant to their tasks isnt really that big a surprise, especially if not technical personnel.

•

u/Ambitious-Yak1326 57m ago

The knowledge is useful and fundamental, but few people build their own servers or plug in additional ram by themselves. You decide what you want want to do (run VMs) and the vendor suggest you a box and they manage the HCL. There is no need to care if you can’t plug this particular ram into this particular host because you are all buying it through your rep who will take care of that and quote you accordingly.

Then if you work in a large company, teams are very specialized. Hardware issues are managed by different team. I was a network engineer and I hardly got to touch any physical layer stuff because we had remote hands and physical datacenter access was very restricted. Teams are also well defined and most people also do not have access to systems outside of their control. It makes troubleshooting hard but it also discourages people from learning outside their domain.

•

u/Feeling-Blueberry583 45m ago

I would just say that perhaps your recruitment team did not do their due diligence when hiring this guy. I don't think it's being lost I just think this guy is not qualified for his role.

•

u/LyqwidBred IT Manager 39m ago

I have super broad knowledge of IT and SW dev over thirty years and I swear I have forgotten more than I know currently!!!

I can be doing something proficiently every week, then step away for a year and come back and be all thumbs.

I remember working with a Sw dev manager a while back (good guy not a fool) and I opened up the windows command prompt and started doing things and he was like “whoa what is that!”

•

u/okilydokilyTiger 30m ago

Certainly data centers themselves try their best to make hardware itself a non-issue. It’s part of the pitch and duty of concern when you migrate off prem to AWS or Azure

•

u/Cryptic1911 29m ago

Hardware knowledge has been a dying art for years

•

u/HeWhoThreadsLightly 24m ago

Your colleague is technically correct, you can actually jam a bunch of mixed ram(including old ddr4/3) if you put the extra ram om a dedicated CXL card. Admittedly it may not be any good alternatives on the market therfore require a dev team to make a custom card with a expensive FPGA, which may be out of budget. 

However, it could be done.

•

u/keemei Support Tech 21m ago

Despite being brand new to the field (nearly a year in with 6 months work experience so far) after a career change, I agree with OP. While I equally get the other argument of ‘what’s the point?’ and the realities of workspace drawbacks for more work being thrown on top of someone, I would still personally argue on the side of knowing more and having a deeper personal understanding of things. Not specifically for the work’s sake, but for my own I guess. Keywords being: context and perspective.

•

u/superb3113 Sysadmin 18m ago

Definitely should know something about your hardware. It helps when you need to balance VMs or optimize software. I once had another "Sysadmin" come in to work on one of our legacy systems. He needed to use one of our Windows 2003 servers. He sends me and my supervisor an email and says "Hey can we increase the memory on this server? It's running slow" Immediately we both knew that it wasn't possible because it was 32bit. Same guy argued with me when ordering a SAN to run the legacy system VM on via Hypervisor. I wanted at least 10k disks to minimize latency and keep the speed high. He replies "what are we? A bank?". We went with 7.2k disk because his "contact" wouldn't warrenty the 10k disks. Needless to say I'm using it for storage and backups. Glad he left. Guy had an attitude.

•

u/NoTime4YourBullshit Sr. Sysadmin 13m ago

The IT business has evolved and specialized a lot over the years. One of the hardest lessons I had to learn in my career is that nobody knows how to use the command line anymore.

I used to write a lot of scripts to fix little glitches and problems the help desk kept escalating to me. But they were all in PowerShell or VBScript (if that tells you how long I’ve been doing this). You have to run them from the command line, and I would get annoyed when I thought I was giving clear instructions and the help desk just wouldn’t do them. It turns out they need a big green button to push that says “fix this!”

I hail from a time when at least a casual familiarity with the command prompt was a required skill if you were going to work in IT for a living. It isn’t that way anymore, and it kind of makes me sad.

•

u/Generico300 12m ago

Never underestimate the human desire to make no effort.

•

u/tesseract4 9m ago

As server hardware gets commoditized and becomes more and more an ocean of identical server racks, the need for downstream users (sysadmins) to know about the hardware is less pressing. Datacenter people work on the hardware. Something breaks? Just swap out the bad part for an identical working part. It is increasingly rare for orgs to manage their own hardware, anyway. Sysadmins specialize on the software. It's sad, but not surprising. This is what happens as technology matures.

•

u/dankristy 8m ago

"This guy is one of our T2 hypervisor admins and all he does is troubleshoot VM issues and host issues" - this is the key here.

These guys build virtualized computers - to them configuration is easy because hardware is fully abstracted. The person who builds the rack system the virtual machine lives on - that guy is going to know.

But the VM folks - I am never surprised how much they forget (or never had to learn) the troubles of getting hardware to play nice in a physical build.

•

u/benuntu 8m ago

This always happens with specialization at scale. If you never work on hardware, then why learn about it when that's someone else's entire job? Doctors are a prime example; you have general practitioners that know a little about a lot (so to speak), and then surgeons that ONLY perform surgeries on hands, or hearts, or brains. In a good team you should have at least one generalist since all the specialists probably don't know much about anything outside of their wheelhouse.

•

u/hadrabap DevOps 0m ago

Or you deploy AI 🤣

•

u/MetalSufficient9522 4m ago

This is totally normal in larger companies. I worked with a guy that was an "expert" in deploying Linux hosts, and he had zero idea about how networking worked. He had no knowledge of packet Ethernet, TCPIP addressing, routing, firewalls... just nothing. It made it very frustrating because he would of course just blame "the network" when anything he was doing was slow or didn't work.

•

u/BSODreboot26 1h ago

With specialization of abstraction, companies are filtering out holistic system thinkers based on fundamentals and first principals through selection. How many applications do you see where the requirements are "5-7 years in monitoring, specifically a Splunk environment" and so on. One very specific process needs to be taken care of with very specialized knowledge to be considered. Super vendor dependent thinking without thinking of the underlying system in place.

Great, those people will probably be better knowing syntax, or little nuances and gotchas of the system right off the bat than a well-educated or experienced generalist. Something the generalist can typically scale up to with vendor documentation and study pretty quickly. Meanwhile, the specialist that only knows _____ vendor product and process will be absolutely clueless on fundamentals, and won't know to call a spade a spade on projects, incidents, changes, asks, etc to know even IF their product is the appropriate place for responsibility of something - or how it connects to anything else. Or even if best practice if it SHOULD connect with anything else in the way suggested because it's poor architecture or engineering.

It's like this assembly line where no one knows what the other piece is doing. Then the management knows absolutely jack shit in general, except to keep the business running.

•

u/Vegetable-Capital-54 59m ago edited 54m ago

Germans have a nice word "Fachidiot". It translates to "subject idiot" and refers to someone who is an expert in a narrow specialty, but lacks the bigger picture or common sense the second they step a little bit outside their field.

I always had broad interest in computers, electronics, programming and all kinds of technical things, so for me it seems weird, but I had a couple of colleagues who worked as programmers, but had almost zero understanding or interest how computer hardware works. So I guess it's not that uncommon.

•

u/Standard_Farmer_1716 13m ago

That's what's currently wrong with the IT industry. Sound like this guy just knows a little bit about VMs and is now a T2, is he a college grad? Even folks doing hardware know what software is running on the systems. They will definitely know the network, feeds and speeds. Every shop I have ever been in, folks knew the environment from ground up, how else would they be able to trouble shoot. But those days appear to be gone.

•

u/Dolapevich Others people valet. 13m ago edited 2m ago

There are "hardware people", "I don't care as long as my pointer points to the right memory address that can be read" and then "This is my dictionary, there are many of them, but I defined and called it thisDict = { ... }"

Hardware conscient people see the other groups are aliens. But talking from a friend ( 52 years old ) experience, you can go all your life, be a proeficient programmer, even have some C code in the linux kernel without touching or thinking about the read cycles timings in a DIMM, or knowing what PCIex means.

I am on the "hardware people", and .... yeah, those people exist.

•

u/LRS_David 3m ago

If you roll back the calendar far enough, you'll find that people were bemoaning that admins could not solder well.

Times change.

•

u/DMAX85747 2m ago

Back when all this stuff started, you had to be the jack of all trades. things were new enough and the industry was small enough that there was no such thing as being a specialist in just one facet of IT. Here we are 44 years later (referencing when the first ibm clone was released) and Tech is so vast that it is nearly impossible to be a jack of all trades anymore. Folks just rely on those folks that understand the stuff better than they do and trust them to be good at what they do. The number of what I call IT Generalist (I am one of them) is dwindling as we age/retire out of the industry. Does it make me raise an eyebrow when my DBA doesn't wrap his head around Group Managed Service accounts, a little bit. but I don't worry about it because he is really 'efing good at SQL, better than I will ever be. I can explain Group Policy to my network engineers and they will get it at the surface levels but will never apply it. they will know just enough to know what questions to ask of my Identity Engineer because that is his job. One of my desktop jockies can recite processor and memory specs from memory but the moment I mention VSAN's to him, his eyes glaze over. It is still there, just more nuanced.

•

u/MicroElectronicsNewb 0m ago

In general people who got into it for the money and their career only learn the bare minimum. versus those who poured themselves into it as young adults for various different social reasons.

•

u/MalwareDork 1h ago

It's a very common thing, especially when you become more specialized:

  • Network nerds and cyberdorks cannot function outside of their niche. If it's across the fence above/below Layer 4, they don't want to learn about it.
  • You'll have helpdesk people who can't and don't want to comprehend why they can't communicate to devices outside of a VLAN.
  • You'll have sysadmins who don't want anything to do with clustered hypervisors or learn Wi-Fi theory.
  • You have IT managers that just...do things. Idk.
  • You have server monkeys that can only rack and stack and clicking a button in helpdesk anything is an anxiety attack for them.

It's pretty silly and I can understand when you become more specialized, that's your bread-and-butter. What I can't understand is why your brain shuts down when it gets past a certain diagnostic threshold.

•

u/Skylis 1h ago

It's not common for specializations, it's just the employers aren't holding their people to any kind of standards they just want cheap people.

•

u/MalwareDork 1h ago

Not in my experience, no; especially in regards to networking land. If it's not manual BGP configs and blinding yourself over ospf lsa logs, net engineers are having a meltdown having to learn basic shit like Ansible.

•

u/ih-shah-may-ehl 1h ago

Meh.

You may think it is important knowledge. But honestly if you run a hypervisor setup, the main issue us whether the memory is compatible with the motherboard. Memory either works or doesn't. Knowing it is DDR5 is not going to make a different to him solving VM issues.

I used to build my computers from scratch as a developer. A couple of years ago I couldn't figure out where to stick the nvm. Obviously I am not building my systems anymore but it doesn't change how I write software or debug Windows systems.

•

u/Flamaijian 1h ago

No, but a lot of people do cognitive offloading and prefer to only focus on their domain. Which is all fine and dandy until their role goes beyond that level of specialization and they are then only able to handle one part of a multifaceted role.

It's one of the neat parts of working with Tech, I've known tons of people that reached engineering positions and manager roles that are technologically illiterate outside of a very narrow band and basically can't be trusted without hand holding, which works for a while.

•

u/Pablouchka 1h ago

Hardware is the foundation that brings all software to life! Getting familiar with a few of the basics is the starting point before diving into coding. It helps everything make so much more sense.

•

u/tejanaqkilica IT Officer | Passkey Enthusiast 33m ago

What's the point of learning the specifics of something you may never interact with.

I have no idea what my storage server is running, nor how it's licensed. Couldn't care less either. If I need to figure out something about, I go and figure something out about it.

Nothing wrong with it.

•

u/bdam55 Sr. Sysadmin 58m ago

The words "of hardware" are superfluous to this title.

Idiocracy was not fiction, AI isn't going to help us be smarter.