Hacker News new | ask | show | jobs
by uneasy-sausage 2630 days ago
I was hoping you could expand on your statement of prospects for those with technical proficiency? What are your thoughts on proper skill investment if some of the skills associated with formal RHCE seem to be decreased.
1 comments

My feeling is that greater proficiency in how code, leveraging the services can serve perspective employers. It's vague and I'm not sure if it can be quantified as easily as the RHCE, so let me give you an example.

With the RHCE you learn about configuring Linux systems. That is building single systems from scratch, configuring firewalls, service files, security configuration and so on. The old format when I took it was the RHCSA would teach you about the system through boot, and the RHCE would teach about how to configure the services, at least that's how one of my instructors put it.

In terms of real world work, at most companies most of this work/process is done in the beginning of their technical life (starting the company or new endeavor) and once you have a method of building servers, and working configurations you don't revisit these concepts as much. Maybe that is what the Ansible cert is supposed to address.

The hard part from an employment perspective is that this work is slowly moving away towards the cloud and all in one solutions which reduce the need for this type of administration.

The big shops have large processes which likely involve solving problems on a more abstract level than what you learn with the RHCE. It's important to know for sure, but likely 95% of these problems are solved on the configuration management, cloud provisioning, or some other level.

On the other extreme, the newer, smaller places aren't going to invest in building Linux servers. They are more likely to maybe have a Windows server/NAS or, more likely, all cloud services at this point.

As an interviewee I have seen this where you grind through technical interviews (about an hour of lots of arcane, frequently out of date questions) and they tend to want either drones to do grunt work with little opportunity for growth, or know their exact technical stack to solve some specific problem.

As an interviewer I see a lot of developer/jack of all trade types trying to sell themselves as system admins whereas its clear that they don't really know system administration. We had one candidate the other day who had worked for close to 10 years in the larger organization who didn't know what /var was. :0

There is still a role for the RHCE style engineers and I had a good time learning it, but at this point I'm not sure where that path will lead in the future.

I think a better use of time would be to learn python or javacript, find a way to apply it to the area you would like to do it, get a green lawn on github, learn how to do something impressive with some public APIs.

Just my 2c as a sysadmin take from it what you will.

I appreciate the feedback. I'm a Junior Windows Sysadmin right now trying to guide myself into a direction. My work is mostly with a cloud-fearing customer who keeps ALL things in-house, so my view of work from inside this chamber makes feel anxious about what the real world is doing/offering. I've noticed that within a vast organization such as the one I work in - the opportunities to perform from zero installs/configurations is pretty much nonexistent and a push to DevOps/automation/cloud tech is more of would-like-to-have and not really a goal that is in the making.

Diving into code such as python and Javascript is probably a good fail safe/transferable skill wherever I end up/doing. I've been leaning towards the whole Linux/CCNA/Networking/Cloud roadmap but am still relatively unsure.

I appreciate your feedback and the opportunity to bounce things around.