> I've realized I can learn pretty much anything on demand. So I find interesting problems and try to solve them, rather than spend alot of time learning frameworks and languages and hope to apply them.
I find this to be a very good approach and it applies to me as well.
Everything I know about "programming" I learned because I needed something done. 10+ years ago I wanted a website, so I learned HTML. Then I wanted a dynamic website, so I learned ASP and SQL. Then I needed some cool interactions, so I learned JavaScript. Then I wanted to create a web app, so I learned Python & Django. When the time comes to build a chat application, I'll learn Node.
This approach enabled me to have much more time to learn new stuff and learn them well enough so as to build production-ready stuff, because that's the goal at the end of day.
The downside is that I rarely have time or energy to just experiment with something new just for the fun of it. It evens out though because I have fun at work learning and doing stuff I actually need to be doing.
I find this to be a very good approach and it applies to me as well.
Everything I know about "programming" I learned because I needed something done. 10+ years ago I wanted a website, so I learned HTML. Then I wanted a dynamic website, so I learned ASP and SQL. Then I needed some cool interactions, so I learned JavaScript. Then I wanted to create a web app, so I learned Python & Django. When the time comes to build a chat application, I'll learn Node.
This approach enabled me to have much more time to learn new stuff and learn them well enough so as to build production-ready stuff, because that's the goal at the end of day.
The downside is that I rarely have time or energy to just experiment with something new just for the fun of it. It evens out though because I have fun at work learning and doing stuff I actually need to be doing.