3 ms·
I've made a point of not bothering to learn new tech environments unless I was interested, and it hasn't made me unable to collaborate. Usually I just learn it
by prewett 3y ago
I've made a point of not bothering to learn new tech environments unless I was interested, and it hasn't made me unable to collaborate. Usually I just learn it on the fly, when I'm asked to do something outside my usual scope at work.
Although I did have a moment of panic when I signed up for a contract work with some OpenGL/C# work. I was hoping to talk them into C++, but I'd used C# before. Turned out to be a TypeScript project using WebGL, neither of which I'd done anything with, so I had a couple of days of panic until I realized that TypeScript was similar enough to C++ that I could get work done while learning.
(Also, if you want to learn new things, doing lots of smallish contracts is a great way to do it. You select the contracts that are doing something new but leverage some of your existing knowledge. These are not hard to find; you'll have a harder time finding something that doesn't require some learning!)