3 ms·
hint to the young: contribute anonymously. go to interviews and talk abou range vs xrange. it might never happen, but when one employer decides to go crazy an
by gcb0 10y ago
hint to the young: contribute anonymously.
go to interviews and talk abou range vs xrange.
it might never happen, but when one employer decides to go crazy and try to blame you for leaking code (that you may have written even before joining them) on open source projects, you are going to regret skipping the silly interviews by showing your open source persona to them. best thing you can do is keep it to yourself. then when you really need it, say for a research grant, then go public.
- woodruffw 10y agoI appreciate the advice, although with the jobs I've had so far I've been sure to tell my employer in advance about my open source work. Maybe I've just been lucky, but all have been either okay with it or actively supportive (even when concurrent with in-house development). That being said, I've been careful to avoid open-sourcing projects that I think come to close to hired work.
- gcb0 10y agowhat you describe is the common sense absolutely everyone have. but it means little when dealing with crazy.