> I know lots of sysadmins and they all automate tons of stuff. They aren’t “programmers” per se, but they wrote a lot of code. Mostly shell or maybe Perl or py

> I know lots of sysadmins and they all automate tons of stuff. They aren’t “programmers” per se, but they wrote a lot of code. Mostly shell or maybe Perl or python or something similar. And they probably assume all sysadmins program and wouldn’t even think to call that out in the job posting. I mean shell I can understand, and Perl to a minor degree because of sed/awk pcre regex, but Python is really getting into programmer territory in my books. I wouldn't call myself a programmer by a long shot, I've written a 6502 state machine in C before, but I'm shocked it works at all, and it's not cycle accurate. For what it's worth, this was some redhat shop who use slurm and foreman/katello... it really did seem like they wanted me to write code to run on their cluster (probably C++). It sucks that I'm stuck where I am now, but it could be worse... so I'm not totally mad they've strung me along, but it would be nice if HR folks would say what they actually mean/want, and be prompt about it. Applicants are people too, and we deserve to know if the job actually exists if we're going to spend the time interviewing and training to get acclimated to whatever setup the CTO/CIO wants us to use to do our job.