4 ms·
It doesn't have to be different; your own employees are developers and can learn to become just as effective at contributing to any given project (and after tim
by jka 5y ago
It doesn't have to be different; your own employees are developers and can learn to become just as effective at contributing to any given project (and after time, many different projects) if you ask them to and provide them with time to learn.
- simonw 5y agoI don't think that's entirely how it would work. As an open source maintainer I would much rather you pay me than pay your own developer - because no matter how talented they are, if they're doing the work I'll need to spend a huge amount of my time discussing the work with them, reviewing their code and generally being a now-unpaid engineering manager to help shepherd their efforts!
- jka 5y agoAs a hypothetical employer of said hypothetical developer, I wouldn't want them to dive straight into the code; I'd want them to demonstrate an understanding of the business and technical problem we face internally, develop some ideas (preferably ones that generalize to other users of your software), and discuss those potential solutions with you. The ideal goal would be to have someone on my own staff who understands and can improve the project's codebase, with your blessing, and who contributes towards the resilience of your project by way of adding numbers (and I'd be happy if they respond to Q&A, within reason, as part of your community, because it's part of my business' dependencies).