I hate it, this is the sort of thing that scares people away from contributing to projects and approaching researchers
Conversation
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Even leaving aside MS objectives (which I doubt are that important here), the question of how best to make Lean accomplish his goals is a hard one. In almost every case, helping someone who doesn't show up with code will take longer than just doing it yourself, and w/ ~0 benefit.
4
1
Yeah, ultimately you have to invest a lot of time in taking chances on people, adding contributing guides, leaving open issues, etc. Eventually that should pay for itself but its a lot of initial overhead that might be hard to justify to superiors.
I don't think the issue is justifying things to superiors. It's whether doing those things actually benefits your project more overall than shipping new features yourself.
2
2
Maybe that's an industry thing, I would have trouble viewing research that way
1
Show replies