Re:How to get people to work on your project (2007)
by mettamage on Thursday June 18, 2020 @08:43AM
(#23562534)
Summary:
1. Make a project
2. Work super hard at it but not to the point of exhaustion (stay optimal/healthy)
3. If you aren't already, become a good programmer yourself (you really need this, if I'm reading the author correctly)
4. Test your code
5. Be capable of dealing with anger, frustration and joy
6. Your biggest issue isn't time, it's your motivation
7. Dare to fail
So basically: build a project and talk to people. He writes about it epic/coach-like way (e.g. "Fail hard. Fail with motherfucking gusto. Succeeding, like flying, is throwing yourself to the ground and missing.").
---
I might need to become good at getting people to work on my project, as I might need to split my codebase in 2 and I would like your input on how to go about it [1].
1. Make a project
2. Work super hard at it but not to the point of exhaustion (stay optimal/healthy)
3. If you aren't already, become a good programmer yourself (you really need this, if I'm reading the author correctly)
4. Test your code
5. Be capable of dealing with anger, frustration and joy
6. Your biggest issue isn't time, it's your motivation
7. Dare to fail
So basically: build a project and talk to people. He writes about it epic/coach-like way (e.g. "Fail hard. Fail with motherfucking gusto. Succeeding, like flying, is throwing yourself to the ground and missing.").
---
I might need to become good at getting people to work on my project, as I might need to split my codebase in 2 and I would like your input on how to go about it [1].
[1, Ask HN: Diverging products: fork codebase, create config file or other option?] https://news.ycombinator.com/item?id=23562286