I’d suggest exposing yourself to new ways to think about problem spaces, rather than spending time diving into specific technologies if you don’t use them on a daily basis. The return on your investment will be higher early on in your growth as an engineer.
Some examples from my own life:
Read Structure and Interpretation of Computer Programs, and work through the exercises. It really helps you grok what coding is, and shows you how to see your programs through the eyes of the machine: as data.
Watch lectures on ethics in computing and data science. With the barriers between data science and computing science blurring more and more, and the power each developer has to impact ever-increasing numbers of people, it is critical that we all think about the culture we build into software.
Take a simple computing problem, such as the classic “fizzbuzz” exercise, and pick a language, and solve it in as many ways as you can. For an added challenge, do this for a handful of different languages. For an even better challenge, choose unfamiliar languages, and/or languages that are drastically different from each other. The main value of this comes from the various perspectives it forces you to think from.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I’d suggest exposing yourself to new ways to think about problem spaces, rather than spending time diving into specific technologies if you don’t use them on a daily basis. The return on your investment will be higher early on in your growth as an engineer.
Some examples from my own life: