4 ms·
Bringing this point back closer to home: I've been a "software professional" of one shape or another for over 20 years now. In my case, that's come with a never
by chronotis 7y ago
Bringing this point back closer to home: I've been a "software professional" of one shape or another for over 20 years now. In my case, that's come with a never-ending need to constantly retool: new languages, new SDKs, new device types, new APIs, etc., etc. I'm sure this sounds familiar. There are a LOT of jobs out there that don't have any continuing education requirement, or where the idea of learning some new computer interface for doing the same work you were doing before adds a lot of friction.
I enjoy the constant learning curve, but not everybody does. Professions that used to last a lifetime, don't any more, but we aren't given those expectations at the beginning of our journeys. Additionally, even though I enjoy the act of learning I'm starting to notice that it takes a little bit more effort year by year to learn the new tricks. And yet our earning potential (which directly drives a wide range of personal and family decisions) is dependent on staying on the treadmill.
I can see the day, eventually, where I'm not as fast a learner as the latest round of college graduates and where whatever wisdom I may have gained isn't of any value or relevance. I hope I am wrong about that.
- robocat 7y ago> In my case, that's come with a never-ending need to constantly retool: new languages, new SDKs, new device types, new APIs, etc., etc. I think over time those things are not as significant as the changes in disciplines (titles?) or verticals. E.g. Changing from an embedded SE to front end UX is more difficult than the languages or tools involved. Edit: is it harder to retrain from front end to embedded? I've traveled the ≈embedded to ≈ux road (via ≈applications). From ≈employee land to ≈owner land.
- chronotis 7y agoTrue, and (so far for me, anyway) it's usually been a slow-motion transition so there's been enough time to get ahead of the wave. Or at least keep up with it...as long as you're paying attention.
- lawrenceyan 7y agoComputer Science at the end of the day is just applied math. The majority of the algorithms and data structures used today in software engineering were invented more than 50+ years ago. The language or framework you use really shouldn’t matter all that much. That’s just a matter of taking some time to acquaint yourself with the vernacular. But fundamentally, the maths stays the same.
- jdnenej 7y agoThe vast majority of real world programming isn't math or algorithms. It's knowing that your framework has all of these algorithms built in already and knowing how to utilise them instead of rebuilding everything from scratch.