> "good projects" or "smart colleagues" Those are very very good for retaining people you already have though, so while not super important for hiring they are

> "good projects" or "smart colleagues" Those are very very good for retaining people you already have though, so while not super important for hiring they are important for keeping the folks you hired (after all, what is the point if you keep losing people you hire). > If you want those and can't get it in your job, well that's what open source work is for. Not necessarily. If your area of interest aligns with your work then even open source work is more productive if you have a use case for it. For example - say my interest is distributed systems, then technically my work will have more impact if it is being used on large clusters with large number of concurrent systems. Open source does not happen in vacuum.