Depending on what kind of work you do, it can also be helpful to learn at least the basics of various "back end" (or "system") languages and libraries out there

Depending on what kind of work you do, it can also be helpful to learn at least the basics of various "back end" (or "system") languages and libraries out there. For example, one of the following in each categories: - something for number crunching and statistics: Python or R (went with Python here, also has nice image/audio processing libraries) - one of the more popular higher abstraction level languages: Node, Python, .NET, Java, PHP, Ruby or another one - perhaps something for being able to create static executables and packaged tools/utilities: Go, C/C++, Rust - maybe something for GUI tools (opinions vary, I still like Lazarus/Pascal, most might go for Electron, others grokk Qt/GTK etc.) Chances are, you won't need all of those in your day job for the most part... until one day suddenly a use case will present itself, where doing it in one of those languages will be easier than whatever you're using already. Plus, it can make for a fun few weekends, if you have the curiosity and time to spare. If you can get your company to pay for you upskilling yourself and don't have to fall into the "1 year of experience, X times" trap by just fixing bugs, even better! Even better if you learn multiple of these and then can reason about which tool might be better for any given job.