3 ms·
I had a job once where I provisioned storage. As in, log into a filer/array (NetApps in my case), create a volume, hand it off typically to system admins that w
by thoth 11y ago
I had a job once where I provisioned storage. As in, log into a filer/array (NetApps in my case), create a volume, hand it off typically to system admins that would then create a VM or use the volume for something else. That was it, my portion was mostly "create volume 500G" and sometimes a few extra configuration steps, like mirroring or setting up replication.
I don't know what that IBM office was doing specifically, but I can easily imagine the situation described in the article!
I looked into moving up the stack, so to speak, as soon as I could because that job was so hyperspecialized it was essentially non-transferable.
- rrich 11y agoAstonishing. Did you realize what your responsibilities would be when you were hired? Could only imagine having to do a full blown tech interview to find out the position was mundane and could be scripted.
- thoth 11y agoNo, the interview was fairly vague and thus partly my fault for not getting a better description. To be fair, the other areas within that office were hardware related (setting up SANs, configuring and cabling them up) so had I stayed I would have learned that. I described it like this to friends who asked: what I wanted was "The Unix/Linux System Administrators Handbook", what I got was "Chapter 8: Storage" or even just the "Disk Partitioning" subsection of Chapter 8 of that book. ;)