3 ms·
Pretty much this I think. I started programming as a career in the last millennium, did desktop stuff for years (Delphi and then .Net) saw the writing on that
by noir_lord 6y ago
Pretty much this I think.
I started programming as a career in the last millennium, did desktop stuff for years (Delphi and then .Net) saw the writing on that wall and moved to the web.
It doesn't have to be a "no life, always learning" thing like some make it out to be, I've gotten good (and patient) at waiting things out, I'll take note of a technology, think that it seems interesting and then keep an eye on it for a year or two - I have an internal list I use to evaluate that, if it looks to still be interesting I'll pick it up at that point when there is a wealth of good material and best practices have shaken out and it's a lot easier to pick up.
The sheer torrent of stuff coming out means no one person could possibly keep track of all of it anyway.
These days I do my 40 hours at work and then maybe 4-5hrs a week looking at stuff that interests me outside of work because I find learning enjoyable and then I do other things and switch off.
- jameshush 6y agoIt's amazing what even ONE hour a week of watching a tutorial that interests you anyway can do. I went through all the RxJs tutorials for genuine curiousity. Even though we don't use RxJs at work, I got really really good at knowing when to use `map`, `reduce`, etc. in code without being too clever. Those two Sunday afternoons did wonders!