4 ms·

It's not about denying you employment. It's about hiring someone who can ship software. If someone has publicly shipped software and you can see that, they make

It's not about denying you employment. It's about hiring someone who can ship software. If someone has publicly shipped software and you can see that, they make for a good candidate. It seems reasonable to me that people who really love writing software and do it a lot would get jobs and be successful in the industry. I wouldn't judge them on their work/life balance, some people really do enjoy programming that much.

LargeWu 7y ago
If you can't glean that devs with 15+ years of experience on their resume know how to ship software, then maybe the real problem is your ability to evaluate talent.
- malvosenior 7y ago
  I've hired tons of developers with 15+ years of experience! A lot of them have amazing OSS contributions. Some don't but all can talk in depth about projects they've delivered. Hiring based on open source contribution isn't the only signal one can look at, it's just a very strong one (the strongest in my experience). I'll add that not all developers with 15+ years of experience can ship software. Many have let their skills deteriorate or never pushed themselves to learn new things. It's yet another reason a strong personal portfolio is a good signal.
- xedrac 7y ago
  I am one of those with 15+ years of experience and have shipped many different projects. I've also interviewed many people with impressive resumes only to realize that resumes don't translate to performance. The ability to ship quality software has more to do with personality than it does resumes. I see nothing wrong with counting open source contributions as a big plus. I wouldn't use the lack of it as a hard filter though.
scarface74 7y ago
There is a huge difference between “shipping software” and doing a git push..... I’ve actually “shipped software” that got put on production servers and people paid money for.
- malvosenior 7y ago
  That's the beauty of it being published on Github. I can look at the project and see if it was just a `git push` of something meaningless or if it's actually well thought out and demonstrates ability.
  - scarface74 7y ago
    That may show an ability to write software. But shipping and putting them on production servers is still different v
    - malvosenior 7y ago
      Shipping is different than deploying server-side code. Going from concept to execution is shipping, and it's what I look for in a candidate. Again, this has worked out very well for me. An added bonus is if you hire OSS contributors, they tend to attract more OSS contributors.
plughs 7y ago
I find it strange to associate OSS contributions with 'shipping software'. I've shipped plenty of software. I've dealt with drop dead release dates, 5 nines HA requirements, production war rooms, and a product paid for and used by millions of people. Is 'shipping software' the same when there are no angry customers who can burn up the support line demanding refunds and threatening to leave 1 star reviews on amazon?
- malvosenior 7y ago
  Being able to produce a solution to a problem where one didn't exist before is "shipping". I've never regretted hiring someone who has multiple projects they've created from scratch.

LargeWu 7y ago

If you can't glean that devs with 15+ years of experience on their resume know how to ship software, then maybe the real problem is your ability to evaluate talent.

malvosenior 7y ago
I've hired tons of developers with 15+ years of experience! A lot of them have amazing OSS contributions. Some don't but all can talk in depth about projects they've delivered. Hiring based on open source contribution isn't the only signal one can look at, it's just a very strong one (the strongest in my experience). I'll add that not all developers with 15+ years of experience can ship software. Many have let their skills deteriorate or never pushed themselves to learn new things. It's yet another reason a strong personal portfolio is a good signal.
xedrac 7y ago
I am one of those with 15+ years of experience and have shipped many different projects. I've also interviewed many people with impressive resumes only to realize that resumes don't translate to performance. The ability to ship quality software has more to do with personality than it does resumes. I see nothing wrong with counting open source contributions as a big plus. I wouldn't use the lack of it as a hard filter though.

scarface74 7y ago

There is a huge difference between “shipping software” and doing a git push..... I’ve actually “shipped software” that got put on production servers and people paid money for.

malvosenior 7y ago
That's the beauty of it being published on Github. I can look at the project and see if it was just a `git push` of something meaningless or if it's actually well thought out and demonstrates ability.
- scarface74 7y ago
  That may show an ability to write software. But shipping and putting them on production servers is still different v
  - malvosenior 7y ago
    Shipping is different than deploying server-side code. Going from concept to execution is shipping, and it's what I look for in a candidate. Again, this has worked out very well for me. An added bonus is if you hire OSS contributors, they tend to attract more OSS contributors.

plughs 7y ago

I find it strange to associate OSS contributions with 'shipping software'. I've shipped plenty of software. I've dealt with drop dead release dates, 5 nines HA requirements, production war rooms, and a product paid for and used by millions of people. Is 'shipping software' the same when there are no angry customers who can burn up the support line demanding refunds and threatening to leave 1 star reviews on amazon?

malvosenior 7y ago
Being able to produce a solution to a problem where one didn't exist before is "shipping". I've never regretted hiring someone who has multiple projects they've created from scratch.