> I always read a lot of blog posts, cool stuff or techniques. You might try writing a blog post. If you're not used to thinking through writing, the results m

> I always read a lot of blog posts, cool stuff or techniques. You might try writing a blog post. If you're not used to thinking through writing, the results may surprise you. Pick a topic you know well, or at least think you know well. Then write about it. You'll soon realize cracks in your understanding you never knew existed. Those cracks contain project ideas. > Afterwards next i'm thinking about the idea and i realize the idea is not fullfilled or not useful for humanity, community, at least for me. You can talk yourself out of any project idea. One way to deal with this problem is README-driven development.[1] You don't want to commit to a project because you don't know if it's worthwhile. You won't know if it's worthwhile until you spend some time on it. How to spend just the right amount of time? Write the README first. [1] https://tom.preston-werner.com/2010/08/23/readme-driven-development.html https://tom.preston-werner.com/2010/08/23/readme-driven-deve...