Live data from Hacker News

On being the employee who “needs improvement”

virtuouscode.com

151–160 of 198 posts

Re: On being the employee who “needs improvement”

#151

Earlier quoted context omitted.

> I tend to get depressed ("cabin fever") if I'm alone all day every day I think we found your problem

Humans are social animals. It's not just "my" problem, it's "most people's" problem.

I see you being downvoted, but I don't get it. I actually work in the office, with 3 teammates nominally there too, but often working remotely, so I spend 2/3 of my days without any of my team around. Even the other teams around me are often out traveling, and I'll be the one tripping the motion sensor to turn on the lights at 9 or 10 in the morning.

It's not comfortable for me as an almost-every-day thing.

Re: On being the employee who “needs improvement”

#152
post #149

Earlier quoted context omitted.

It really depends on how the team was being run. Some remote teams are like co-located teams and work synchronously with set office hours. Other remote teams work asynchronously instead and individuals are free to arrange their work and life as they see fit. In the latter case, if somebody is working on a task that'll take a few days, not hearing from them for a day or two isn't unusual or a problem. It sounds like p…

I've never seen a remote setup wherein being unreachable for more than 1 day during normal work days would come across as legit. It sounds downright unprofessional.

It's not. You're judging asynchronous/remote working styles according to synchronous/co-located standards. There isn't necessarily any such thing as a "normal work day". Monday–Friday 9:00–5:30 isn't 100% applicable when your team members aren't in the same time zones or observe the same national/religious holidays. So long as they get the work done when they say they will, the exact hours they work aren't important.

Re: On being the employee who “needs improvement”

#153
post #92
post #18

Earlier quoted context omitted.

I think that is a somewhat cynical view of the matter; I appreciate that "American Work Ethics" are highly flawed and mostly theatrics (I say this as an American expat who has experienced work from all over the globe), but as much as there is management theatrics in the US, there's also a lot of "woe is me" from employees when they're disciplined. I'd really hate to see how the author of the piece would have reacted…

I've worked blue collar jobs where bosses are way more direct, like your Russian managers - and it's better. I remember one who would tell me most mornings, "Try not to fuck up today!" When a boss is angry and direct in giving feedback, we don't become resentful; we get scared for a while, then settle down. It's the natural way of hierarchy. We all need course correction from time to time, and the modern white-collar…

Time is a multiplier on a lot of issues. There are a lot of things that are essentially non-issues if addressed immediately, which can be problems if they linger. I think the white collar world could do with more directness!

Re: On being the employee who “needs improvement”

#154
post #102

Earlier quoted context omitted.

Lots of places offer flexible business hours, even for people coming in the office. Not everyone always takes lunch at the same time either. Even people in the office are not 100% available all the time. Your attitude towards remote workers seems unnecessarily hostile.

You're misinterpreting my post. At my current job we are flexible -- people come in and leave at different times, eat lunch at different times, etc. I'm not expecting everyone to be at their desks from 10-6 all day every day. That's why I said "core business hours". There's a difference between someone who is unavailable because they're off eating lunch and someone who is incommunicado for many hours at a time and im…

Our team is usually fully remote. I've actually worked my full career in mostly remote positions (15 years now). I've very rarely experienced people randomly disappearing for hours at a time, and usually a simple text will clear things up. However, if you work in a flexible office and your team has core business hours, official or not, your manager should probably convey this. This just falls under "managing expectations", and is not necessarily a failure of the employee.

Sometimes emergencies will necessitate missing even core business hours. This is more a matter of having more responsibilities (family, kids, etc) than being remote though. But if an employee has these sorts of responsibilities, I'm guessing they are more likely to take up remote work.

There are positives and negatives to hiring remote workers, and I think there are several ways to compensate for the negatives. Obviously since I work remotely I think the positives outweigh those negatives. But I also think placing so much emphasis on one of the negatives, that I rarely experience in practice, is extremely narrow sighted. But maybe your remote workers are bad at working remotely, maybe your company is bad at managing remote workers, or maybe there's confounding variables like the one I mentioned above.

Re: On being the employee who “needs improvement”

#155

Earlier quoted context omitted.

It's also not clear to me how pay-for-performance and promote-for-performance is supposed to work without some kind of systematized performance review system. And I will say that, at least in my personal experience, pay-and-promote-for-performance is hugely important in getting the most out of your software engineers.

Performance based pay and the whole hr infrastructure around it is designed to lower the pay quanta it has < 1% to do with rewarding performance.

Why do you say that? And what exactly do you mean by "pay quanta"? Rewarding and incentivizing high performance seems to obviously be in the business's best interest, so why do you say they don't focus on it, even for the companies that do it explicitly for that reason? Are you claiming they're lying as to their motivations?

Re: On being the employee who “needs improvement”

#156
post #154

Earlier quoted context omitted.

You're misinterpreting my post. At my current job we are flexible -- people come in and leave at different times, eat lunch at different times, etc. I'm not expecting everyone to be at their desks from 10-6 all day every day. That's why I said "core business hours". There's a difference between someone who is unavailable because they're off eating lunch and someone who is incommunicado for many hours at a time and im…

Our team is usually fully remote. I've actually worked my full career in mostly remote positions (15 years now). I've very rarely experienced people randomly disappearing for hours at a time, and usually a simple text will clear things up. However, if you work in a flexible office and your team has core business hours, official or not, your manager should probably convey this. This just falls under "managing expectat…

I think the answer is that the remote workers were just bad/slackers/not devoted to their jobs. As I said, they failed to move upwards in the company and some were even fired. This was not at a company that was a particularly good or high-paying place to work, mind you. Maybe you've been luckier in the caliber of people that you've worked with, but I contend that, in general, across the entire workforce, it's not rare to see people taking liberties with remote work.

Re: On being the employee who “needs improvement”

#157

Earlier quoted context omitted.

Humans are social animals. It's not just "my" problem, it's "most people's" problem.

I see you being downvoted, but I don't get it. I actually work in the office, with 3 teammates nominally there too, but often working remotely, so I spend 2/3 of my days without any of my team around. Even the other teams around me are often out traveling, and I'll be the one tripping the motion sensor to turn on the lights at 9 or 10 in the morning. It's not comfortable for me as an almost-every-day thing.

Too many people think that what works for them must be ideal, and should work for everyone. I honestly think that most people will not thrive in a fully remote, work-from-home environment.

Re: On being the employee who “needs improvement”

#158
I've been this person. I was not only somewhat surprised, I also felt betrayed. It was apparent that complaints had been building for some time, but I heard very little of those complaints in the form of direct feedback. It was only in hindsight that I realized my coworkers had been subtly dropping hints for a while.

It sucked. Then again, I actually did kind of suck at my job, too. So maybe the real lesson here is that sucking at your job sucks, not just for you, but for your managers and coworkers too (albeit for different reasons).

Re: On being the employee who “needs improvement”

#159

Earlier quoted context omitted.

I see you being downvoted, but I don't get it. I actually work in the office, with 3 teammates nominally there too, but often working remotely, so I spend 2/3 of my days without any of my team around. Even the other teams around me are often out traveling, and I'll be the one tripping the motion sensor to turn on the lights at 9 or 10 in the morning. It's not comfortable for me as an almost-every-day thing.

Too many people think that what works for them must be ideal, and should work for everyone. I honestly think that most people will not thrive in a fully remote, work-from-home environment.

Too many people think that what works for them must be ideal, and should work for everyone.

Agreed.

I honestly think that most people will not thrive in a fully remote, work-from-home environment.

That may well be true. But there's clearly a non-negligible group that swing very much the opposite way. What we're looking for is flexibility, not one-size-fits-all.

Re: On being the employee who “needs improvement”

#160
post #149

Earlier quoted context omitted.

I've never seen a remote setup wherein being unreachable for more than 1 day during normal work days would come across as legit. It sounds downright unprofessional.

It's not. You're judging asynchronous/remote working styles according to synchronous/co-located standards. There isn't necessarily any such thing as a "normal work day". Monday–Friday 9:00–5:30 isn't 100% applicable when your team members aren't in the same time zones or observe the same national/religious holidays. So long as they get the work done when they say they will, the exact hours they work aren't important.

No, I'm judging by my extensive experience co-working with remotes. No "time zone" makes it legit to be non-responsive for over 24h during work days. It's 100% ok to be not working but that's referred to as "day off" and should be communicated as such.
Post reply on HN