5 ms·

> Always makes me wonder how many dysfunctional companies are out there letting deadbeat remote employees collect paychecks and do as little work as possible be

> Always makes me wonder how many dysfunctional companies are out there letting deadbeat remote employees collect paychecks and do as little work as possible because nobody cares enough to press the issue. I can't imagine it's much worse than it was in the before-times. Wally has always been able to skate along with a certain amount of meeting-attending.

mavhc 5y ago
If you can't tell whether your employees are working, why do you even have employees? Imagine how much money you'll save.
- smorgusofborg 5y ago
  Then you have to get out of all the work you were assigning them yourself. Much better to leave it to a specialist!
  - nmstoker 5y ago
    Yes, but remember in the scenario you're replying to, you cannot tell if they've done the work. So assigning to the specialist you mention might as well mean tossing the job requests into the bin.
- gedy 5y ago
  Most companies I've worked for use "I can see them at their desk" or meeting attendance as the primary measure of "your employees are working".
  - mavhc 5y ago
    don't they do work you can see?
- lordnacho 5y ago
  It's like the adage about advertising: you don't know which ones are effective.
rcurry 5y ago
I worked for a computer security company once, it was my first real programming job and I had no experience with the kind of crazy stuff that goes on with hiring, I was really naive and had no clue that certain kinds of people existed in the workforce. So one day my boss (CTO) calls me up and says “Hey, we are hiring another Windows guy, can you do a quick interview and check him out?” (I was the only Windows dev at the time) So they send me the guy’s resume and he’s a PhD in Electrical Engineering. I feel really nervous about having to interview the guy because he had a PhD, but I figured other people had already checked him out so I meet with him and just have kind of a softball interview, not going into a technical deep dive or anything like that. He seems alright and has a ton of experience, so I figured what the hell. Well about a month later my boss calls me again and he’s like “Hey, we’ve been having some concerns about John Doe, can you check in on him and see how he’s doing?” So I go over to John Doe’s office and sit down with him and talk about what he’s been doing. He shows me that he’s having trouble with some things that are so basic that it’s almost like he’s never even seen a Windows machine, much less done any programming on one; and I’m not exaggerating, it was really that bad! Long story short, they let him go. A few days after, I’m in the break room and one of the Unix guys walks in. He asks me how things are going and I’m like “Well, not so good, we’re back to just one Windows developer because they had to let the new guy go.” He says “Who was that?” So I tell him “this guy John Doe…” and before I can go any further he exclaims “Good God! Not THE John Doe?!?” Apparently this guy was a legend in the IT community in the city - he would fake resumes and get hired for as long as he could run the scam.

mavhc 5y ago

If you can't tell whether your employees are working, why do you even have employees? Imagine how much money you'll save.

smorgusofborg 5y ago
Then you have to get out of all the work you were assigning them yourself. Much better to leave it to a specialist!
- nmstoker 5y ago
  Yes, but remember in the scenario you're replying to, you cannot tell if they've done the work. So assigning to the specialist you mention might as well mean tossing the job requests into the bin.
gedy 5y ago
Most companies I've worked for use "I can see them at their desk" or meeting attendance as the primary measure of "your employees are working".
- mavhc 5y ago
  don't they do work you can see?
lordnacho 5y ago
It's like the adage about advertising: you don't know which ones are effective.

rcurry 5y ago

I worked for a computer security company once, it was my first real programming job and I had no experience with the kind of crazy stuff that goes on with hiring, I was really naive and had no clue that certain kinds of people existed in the workforce. So one day my boss (CTO) calls me up and says “Hey, we are hiring another Windows guy, can you do a quick interview and check him out?” (I was the only Windows dev at the time) So they send me the guy’s resume and he’s a PhD in Electrical Engineering. I feel really nervous about having to interview the guy because he had a PhD, but I figured other people had already checked him out so I meet with him and just have kind of a softball interview, not going into a technical deep dive or anything like that. He seems alright and has a ton of experience, so I figured what the hell. Well about a month later my boss calls me again and he’s like “Hey, we’ve been having some concerns about John Doe, can you check in on him and see how he’s doing?” So I go over to John Doe’s office and sit down with him and talk about what he’s been doing. He shows me that he’s having trouble with some things that are so basic that it’s almost like he’s never even seen a Windows machine, much less done any programming on one; and I’m not exaggerating, it was really that bad! Long story short, they let him go. A few days after, I’m in the break room and one of the Unix guys walks in. He asks me how things are going and I’m like “Well, not so good, we’re back to just one Windows developer because they had to let the new guy go.” He says “Who was that?” So I tell him “this guy John Doe…” and before I can go any further he exclaims “Good God! Not THE John Doe?!?” Apparently this guy was a legend in the IT community in the city - he would fake resumes and get hired for as long as he could run the scam.