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

I respect the sentiment, but for me, this is literally the worst advice i could get, and i suspect it is for other people too.

Your whole comment is centered on the technology you use, not what you're doing with it. Also you're talking about every of those piece of tech like it's easy to do something in it. But see, when you switch technology with every project, even if you learn plenty of things, you :

1. Prevent yourself from becoming really fluent in one piece of technology. 2.Force yourself to learn a myriad of details that are really useless to what you ultimately want to do.

Ultimately you can burn yourself out, learning 1000 things, and all you have to show for it at the end is a collection of unfinished crap projects.

My advice for somebody who feels like this would be quite the opposite :

- Find what you want to do

- Think about it, in a technology agnostic way

- Pick your technology, pick the technology you're the most familiar with at the moment you start realizing the project, even if it seems dull to you, if you're sensible to the kind of syndrome outlined in the OP, it probably isn't :)

- Do it. Don't switch techs.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: