|
|
|
|
|
by yowlingcat
2500 days ago
|
|
I don't know if I agree with your premises or conclusions. I think employers prefer engineers who are effective and have a past track record of success. For some companies, some of these are going to have a "can't rip my keyboard out of my hands" characteristic, but I've mostly found that working on software outside of work has minimal correlation with productivity. Engineers that are steadily growing and continuing that professional growth may work on things outside of work. But they definitely ensure that whatever they do at work, in those 8 hours a day when they're on the job, is in large part contributing to that. IMO, that's 99% of it. Engineering off the job or on a side project? It indicates a certain degree of intrinsic fascination. But if that's targeted in the wrong direction, it can result in someone being distracted and building the wrong thing really well. It varies. |
|
I have talked to startup founders who were very explicit that they only hired developers who coded obsessively outside of work. One was very clear: If you didn't have a public Github profile showing a track record of frequent commits on personal project outside of work hours, you would not be hired at his firm.
> I've mostly found that working on software outside of work has minimal correlation with productivity.
Same. That doesn't mean everyone is hiring based on that.