I'm not young at all, but I'll write my personal opinion and what I'm saying to new engineers. Of course, there may be pros and cons.
I'm doing so-called embedded work, but I'm a software-oriented and not very embedded race.
Generally, one for each of the following three types.
Whether or not this grouping is correct, C / C ++, Java, C #, etc.
C is the best way to know the movement of programs and the movement of computers. Not called assembler. It can be an assembler, but it depends on the processor. You should know the concept.
However, if it is not absolutely necessary to use C in practice, I really want to avoid it. Because the difference in skill is directly linked to the quality of Moro.
After that, it's hard to be object-oriented. It's different from being able to do that. I like C ++, but the specs are so chaotic that it's a completely maniac world. If you can, Java can be used in practice, and it may be good because you can get used to object orientation.
C # was also easy and easy to understand. I only use it on Windows.
Ruby, Python, I'm not using it anymore, but is the veteran Perl? anything is fine. If you can use something, the idea will be almost the same and the application will work.
The scripting language can do anything transcendentally. Even product development can improve personal work efficiency. Therefore, it will be useful in various situations if it can be used.
JavaScript
Or rather, TypeScript?
This is another option for the client system. Even embedded systems have a built-in Web browser these days, and are a must-have item for UI.
You can do anything on your desktop with node.js.
However, node.js is one of the worlds and it doesn't feel light at all.
The above is not an exhaustive form, but if you work on the above policy, even if you have to learn something new, some skill will be the basis for application.
If anything, it is more important to acquire skills of libraries and frameworks than the language itself, but it is unfortunate that it takes time to acquire the prerequisite knowledge to master it, so skill acquisition is effective to some extent. It is good to do it.
On top of that, technology is practice (skilled) rather than knowledge, so it would be great if you could be aware of creating many opportunities to write.
Recommended Posts