Re: Cloud native MFPs
While it's good to have specialists for each side of the house, it's certainly a lot cheaper to recruit from within.
I don't have a huge staff, but when I've had interns or other newbies whether they're for the print or IT side of the house they all start with basic troubleshooting of a printer and copier and the theory of a laser printer. It's a good introduction to embedded systems and also gets them thinking about hardware.
A few years back, the nephew of a friend of mine wanted to get some experience in IT so I took him on for a summer before he started college. He'd never had to troubleshoot hardware before, so we started with a few old printers and went through all of the things to look at: feed rollers, media, fusing, imaging. He got pretty good at knowing what to do and also got up to speed with computer issues beyond just how to install Windows. When he got a job while in school he moved up pretty quickly since he actually knew how to troubleshoot. All of those things a copier tech takes for granted like reading a service log, looking at sensor output, or even putting a machine into a free run are all the things his coworkers didn't do.
It took him a few weeks with me to see that the process to diagnose an issue is the same no matter what it is, and while those first few weeks of printers bored him some, he later told me it showed him how to think about an issue and what could cause it.
Last I knew he was the IT manager for a company out in Nevada.
Sent from my BlackBerry using Tapatalk
While it's good to have specialists for each side of the house, it's certainly a lot cheaper to recruit from within.
I don't have a huge staff, but when I've had interns or other newbies whether they're for the print or IT side of the house they all start with basic troubleshooting of a printer and copier and the theory of a laser printer. It's a good introduction to embedded systems and also gets them thinking about hardware.
A few years back, the nephew of a friend of mine wanted to get some experience in IT so I took him on for a summer before he started college. He'd never had to troubleshoot hardware before, so we started with a few old printers and went through all of the things to look at: feed rollers, media, fusing, imaging. He got pretty good at knowing what to do and also got up to speed with computer issues beyond just how to install Windows. When he got a job while in school he moved up pretty quickly since he actually knew how to troubleshoot. All of those things a copier tech takes for granted like reading a service log, looking at sensor output, or even putting a machine into a free run are all the things his coworkers didn't do.
It took him a few weeks with me to see that the process to diagnose an issue is the same no matter what it is, and while those first few weeks of printers bored him some, he later told me it showed him how to think about an issue and what could cause it.
Last I knew he was the IT manager for a company out in Nevada.
Sent from my BlackBerry using Tapatalk
Comment