Something I've always wanted is "a Netflix queue for tech I want to learn" Ideal features would include: - a regular review of the things you've listed to see if they're still relevant and to help you prioritize - a way to see what's trending amongst everything you've listed (ex. I have three front end web frameworks on my list but React is collectively popular, so perhaps I should start there) - it could notify you…
Ask HN: How do you decide what to learn next?
41–50 of 104 posts
Re: Ask HN: How do you decide what to learn next?
#42Work on my own idea.
Another option; work on freelance projects. Earning could be a good motivation to learn new stuff. At least it is for me.
Re: Ask HN: How do you decide what to learn next?
#43- create a list of all the tools/products/whatever you use at work
- rate them from 1 to 5 (5 you are an expert on this topic)
- then pick the most important one for your job and try to increase your grade
The grade is totally subjective, but still it helps.
For the "next big thing" I take a look regularly to the thoughtworks radar [1]. That's a nice overview.
Re: Ask HN: How do you decide what to learn next?
#44I am doing a series called 52-technologies-in-2016 https://github.com/shekhargulati/52-technologies-in-2016 where in I learn a new technology, build a small app, and blog about it every week. I maintain an Evernote where I write down all the interesting topics or projects I find. I go through the list and randomly pick any topic that excites me that day and then work over the weekend to publish something. This helps…
Re: Ask HN: How do you decide what to learn next?
#45Re: Ask HN: How do you decide what to learn next?
#46Something I've always wanted is "a Netflix queue for tech I want to learn" Ideal features would include: - a regular review of the things you've listed to see if they're still relevant and to help you prioritize - a way to see what's trending amongst everything you've listed (ex. I have three front end web frameworks on my list but React is collectively popular, so perhaps I should start there) - it could notify you…
Re: Ask HN: How do you decide what to learn next?
#47I am doing a series called 52-technologies-in-2016 https://github.com/shekhargulati/52-technologies-in-2016 where in I learn a new technology, build a small app, and blog about it every week. I maintain an Evernote where I write down all the interesting topics or projects I find. I go through the list and randomly pick any topic that excites me that day and then work over the weekend to publish something. This helps…
Sounds cool, how much time do you spend every week?
Re: Ask HN: How do you decide what to learn next?
#48Something I've always wanted is "a Netflix queue for tech I want to learn" Ideal features would include: - a regular review of the things you've listed to see if they're still relevant and to help you prioritize - a way to see what's trending amongst everything you've listed (ex. I have three front end web frameworks on my list but React is collectively popular, so perhaps I should start there) - it could notify you…
I want this for everything. Music to listen to, books to read, guitar skills to learn next, etc
Re: Ask HN: How do you decide what to learn next?
#49Something I've always wanted is "a Netflix queue for tech I want to learn" Ideal features would include: - a regular review of the things you've listed to see if they're still relevant and to help you prioritize - a way to see what's trending amongst everything you've listed (ex. I have three front end web frameworks on my list but React is collectively popular, so perhaps I should start there) - it could notify you…
someone please do this!
Re: Ask HN: How do you decide what to learn next?
#50If I have two topics on the top of my list, and I expect one of these to provide new mental tools, or meta insights about learning or cognition, I'll pick that one.
I also give a higher priority in general to techs that will cascade into improving my speed on future projects in the most generic way. For example I consider that learning how to automate something is never a lost cause, even if I can do it manually at the same speed, because it increases my knowledge about automation, which will be useful down the line.