Hacker News new | ask | show | jobs
by wcummings 3357 days ago
>The people I know who are like this are what I'd describe as "9-5" employees, don't learn anything outside of work

So, you just don't hire people with kids, medical problems or other responsibilities outside of work? If you want people to bone up give them time during the work day, have sr. devs run workshops on new tech you're adopting. Don't create the expectation people should work in their time off. If you want effective employees you should invest in that and not shove the cost onto the individual.

Even if it produces the results you'd (which is pretty questionable) like these kind of criteria have obvious and well-known biases.

1 comments

> Don't create the expectation people should work in their time off.

I have no such expectation, nor did I say people should work in their time off.

I think people need to keep up their education. Learning doesn't stop when you graduate. Your company should be willing to pay for training/courses/conferences, but I also think people that are passionate about things will naturally grow on their own.

At the least, this might mean staying current with news and/or community, especially within your current toolset/ecosystem. As an example, if you don't usually know within at least a week or so that your main language/framework/database/etc has a new release, you're in this category if people I'm talking about.

And to clarify when I say "9-5" I mean the type of person that always has their stuff packed up and is walking out the door by 5:01pm. This tells me either you've stopped in the middle of something, which means instead of staying for 10 or 30 minutes to finish it you will take two hours tomorrow to regain context, or that when you're done something and it's after say, 4 o'clock, you just don't start anything new.

I don't believe in working crazy (or even just 'extra' hours beyond what you're paid for): that leads to burnout and that is bad for literally everybody. I do think it's better to stay longer to finish and not waste time on the context switch of going home, or other days just leave "early" if you are done and can't finish anything further.

Why isn't it acceptable to leave in the middle of a project? If I have a very regular after-work schedule (like picking kids up from daycare), I don't understand why I shouldn't leave at exactly the same time every day. Even if that means leaving something unfinished, that I'll get back to when I get back in the morning. And I might not have anything I can "do" by leaving 30 minutes early, because I can't go home and I can't get to (regular obligation) early.
I think you are dramatically overestimating the amount of waste that results from context switching.