Hacker News new | past | comments | ask | show | jobs | submit login

I generally hate anything that I build that doesn't have a solid business plan with customer need behind it (read: all non-employed side work).

I still don't know how to get out of that mindset.




You can separate projects for learning technologies and projects for customer need. For example, when I wanted to learn Elixir, I made a simple to do list with concurrent users to test Elixir's scalability. A to do list is nothing new for customers but it still enabled me to learn more about the tech. Often, these two categories intersect over a large enough set of projects.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: