3 ms·
They are transferrable. You'll still have a learning curve but it'll be shallower than if you didn't know any development. Not only that, but open-mindedly exp
by richmarr 11y ago
They are transferrable. You'll still have a learning curve but it'll be shallower than if you didn't know any development.
Not only that, but open-mindedly exploring new ways of doing things once will make you a better web dev, make it easier to learn the next thing, and keep you from getting stuck in an identity trap, i.e. "I am a COBOL developer" rather than "I know lots of COBOL (but moved on when the market did)"
Just watch out for the typical 'developer new to a language and tries to make everything just like their old language' trap.
...and the 'I now know a dozen architectural approaches to solve this problem so suffer from paralysing indecision' trap.
Also, recommend reading "Zen and the Art of Motorcycle Maintenance". It's short and has a nice take on skill transferability
- hackaflocka 11y agoAppreciate the answer. I have read ZAMM. I remember the quote about how the an artist making a painting isn't very different from a motorcycle mechanic maintaining a motorcycle. That ultimately it's about applied quality.
- richmarr 11y agoExactly, maintain the mindset that you can absolutely master the problem once you've learned your way through it and you'll be fine. It's a pain to have to re-learn libraries and APIs, but new idioms are always interesting. It's also important not to get caught up in the tribal ego-driven BS, or bias that says one idiom is better than another because it happened to be the way things are done in a previous language or framework. Maybe that's a general problem, or maybe it's heightened in the software world because we're (statistically speaking) a bunch of overprivileged daiper-babies.