Hacker News new | ask | show | jobs
by cnkeller 4599 days ago
This.

While I understand that many people enjoy writing code and do so for fun, there are a large number of fantastic engineers that don't (myself included). Just as I wouldn't give someone preference for a robust profile, I'm not going to penalize someone for lack thereof. There is only so much time in the day and if they can do ten hours worth of work in eight hours and choose to spend their off time with their family, friends, or hobbies, good for them. Knowing how to decompress and enjoy both work and life is just as valuable to me as crafting solutions to engineering problems.

2 comments

If you are working with the same technology stack we work and are not finding bugs or implementing new features you are not playing in the same league.

We don't contribute to FOSS because we are hobbyists or good Samaritans, we do it because we need the features or fixes. We do it because in the long term it is cheaper and more efficient than maintaining a fork or developing a closed source component.

Many software developers don't work with FOSS technology at work. I work in embedded systems and much of the library code I work with has been provided by manufacturers of the devices I'm using. I do find bugs in it and report fixes to the library developer, but they often have strange licensing and don't use github (or even public version control) so this work doesn't end up visibly attributed to me in public.

This doesn't mean that the people working in non-web industries "are not playing in the same league" with respect to skill, it just means that they don't have a huge public representation of the work they do.

> While I understand that many people enjoy writing code and do so for fun, there are a large number of fantastic engineers that don't (myself included).

Sure, but there aren't many people who hate coding but still do it (in significant amounts) in their free time. so having a github profile is still a positive signal towards being a good coder (assuming, of course, that practice causes improvement).

It would be wasteful for a company to ignore this information.

> It would be wasteful for a company to ignore this information.

Very. All I'm trying to say it's not something you should even look at until you're later in the process of hiring.