Originally Posted by ditkaworshipper
OK, so you admit that you can't interview people and you're complaining about the results? Sorry, no sympathy here on that one.
On a positive note, you are seeing good reasons to develop your people skills. It's important to be able to judge what you can get out of people and to interact at a level that they will want to work for/with you, or else you will end up with a lot of situations like this guy throughout your career.
Of course, maybe you like consistent 55-60 hour weeks from picking up slack.
I didn't interview the guy, other people did. However, if I did interview him, I guarentee I wouldn't have liked him. I fixed the 55-60 hour work weeks; they're down to 45-50 hours. Instead of having him "assist me" with my monthly reports, I transfered ownership of them to him. They're so watered down with documentation and automation that he should be able to do them, yet he somehow finds a way to mess up every step. In the workbooks, there's basic macros, vlookup, index, match, offset, indirect, arrays, pivot tables, SQL, ifs, conditional format, etc. I'm not trying to say I'm an expert at computers, but there's enough good stuff available for him to use as a learning aide if he actually cared about learning. You would think he would take the time to actually understand what's going on when he presses buttons, but no, he's a lazy f*ck. Now he's solely accountable for his failure, and I look forward to him making a major mistake because it will happen. Meanwhile, I get to do the stuff I've been wanting to do for a while 1.) research and fix known deficiencies in our standard processes and 2.) research and solve known data errors.