4 ms·
To sit on the sidelines and wait till the technology and market matures is a smart decision. There's a lot of new things popping up, and not everything sticks.
by treve 10y ago
To sit on the sidelines and wait till the technology and market matures is a smart decision. There's a lot of new things popping up, and not everything sticks. This is particularly true if you're running a business and you need to pick the right tech.
Learning a new language though is not a wasted effort, even if eventually the language becomes obsolete. It only takes a few days to get going with something new, and the lessons learned are useful regardless of if you use the language in the future or not.
But to say that there's no interest at all is pretty ridiculous, and there's plenty of people looking at rust and deploying it. That last statement made me feel you might just be a bit burnt out by change in general. Don't lose perspective. Going out of your comfort zone might be exactly what you need.
- blub 10y agoBut one doesn't pick what to learn just between several languages, in fact I think they're a pretty poor investment after a certain count. When learning Obj-C I didn't get much out of it. I like several Swift idioms, but it was hardly worth it to learn a language for that. In contrast I finished an architecture course recently that I expect will bring me 10x value of knowing both of the above languages. Please see my answer to vvanders regarding interest vs industry interest.
- sotojuan 10y agoWhat's the architecture course? I've been meaning to move from learning languages and APIs to learning more "lasting" things.
- blub 10y agoIt was a course based on the book Software Systems Architecture by Rozanski & Woods. The trainer was Rebecca Wirfs-Brock. Reading the book should be a very useful first step when learning about architecture. If one decides to go to the course it's essential that there are also experienced architects participating and that one has an architectural case study that can be discussed.