It’s an interesting thing being in the world of technology. I’m well aware of new applications that simply make life easier and more manageable yet could threaten the very job security that I hold so dear!
Better hardware, more effective software, and better processes threaten the “traditional” job roles.
For example, I know personally a number of friends in the storage space who have lost their jobs because a lot of the software around storage management and automation is now so good that that particular role is no longer needed.
Sure, they might have had a better shot of staying on if their resume was a little broader, but it’s an interesting thing to think about nonetheless.
But, perhaps in ministry it’ll always be a bit different? There’s a relational component to most of what we do, right?
Just some random thoughts.
Stuart says
It’s an intersting thought process and one I’ve undertaken for my own role (network analyst / engineer). With the recent spate of outsourcing stuff to 3rd world countries to save money (and I’ll tell you now this is the bottom line no matter what they shout about quality, etc) then I’ve been asked by friends a number of times how my job fares.
Fortunately they will always need a physical presence on the ground locally to push power buttons, read the status of lights, etc that I will always have a role of some form in my elected career path. Whether I make the most of that role or feel fulfilled is an entirely different conversation.
In short – yes, I believe we will always have Sys Admins, etc, locally.
Graham says
I’m currently acting as IT director in addition to my other capacities as all around “Media Director”. I do very little IT work. Not because our system is so awesome… because it’s not. But because I don’t know a lot about it. Even though I’m not familiar with the inner workings of DHCP servers and all that blobbity bloop, we’ve been able to hang on and hire out professionals for the stuff beyond my abilities. So I suppose you’re question rings true at my church. There is no ‘full-time’ IT guy.
danielcberman says
Until we have complete AI, Self-diagnosing, Self-repairing, self-assembling computers and IT hardware there will always be a need for someone to make sure everything is running as it should, even if the ultimate task is delegated out. It all goes back to the whole dynamic in leadership between direct control and delegation. And even when IT gets to that point I mentioned, there will still be a need for someone to watch over the IT to make sure it still desires to serve mankind or atleast will not harm mankind.
Aaron Melton says
I believe there is a stigma attached to the word “administrator.” I’m quick to correct anyone that labels my position as a “network administrator” rather than “network engineer.” Perhaps I help facilitate that stigma but I believe my job requires too much technical expertise to be labeled as “administrative.”
Stuart says
Is there really a stigma or is it a self-imposed one? Genuine question as I’m not havign a go.
In my time I’ve been known as a Network Engineer / Analyst / Technician / Support Personel / Administrator and there are probably others I’ve forgotten. Sometimes network is replaced with Telecommunications or Comms but it all means the same thing and personally speaking I don’t give a monkeys what the job is labelled.
Oh yes, just remembered, at one stage I had teh longest job title in IT – it was “Principal Community Network Support Officer” – or IOW I looked after networks 🙂