@hobbit666 said in Topics of Systems Administration:
e.g. I'm down as being Infrastructure/Network Manager. But in peoples views where do my duties start and end?
(But maybe this is for another topic)
Well the first question is, why is "network" mentioned, given that that's a subset of infrastructure? That's like saying you are a vehicle/car mechanic. Saying you are a network manager, if that's all you are limited to (85% of the time at least) is one thing (I doubt this can be true, network anything doesn't exist outside of the enterprise space, even companies with many thousands of people generally don't need even a single dedicated network focused role), makes sense. And if you cover everything in the infrastructure space, but don't cover things like helpdesk, databases, applications, etc., then infrastructure makes sense (that would include systems, networks, platforms, etc.). But stating both doesn't. Either you are focused enough to say network and infrastructure doesn't apply. Or you are broader and should say infrastructure, and network doesn't apply.
But then "manager" becomes a question. Admins run things, managers manage people. The terms are used very loosely outside of IT, but inside of IT they generally aren't. You admin hardware/software, you manage people and vendors/businesses. The title "IT Manager" is generally considered to be (and this holds up very universally when you talk to people) someone focused on managing people under them and/or vendors. But an IT Admin, would not be assumed to manage people or maybe not even use vendors, and just administer everything that falls under IT.
