To me the syntax is the least problematic - Ruby, Python, Node, PHP... they're not that different looking syntax-wise. For me it's definitely the CLI, package

To me the syntax is the least problematic - Ruby, Python, Node, PHP... they're not that different looking syntax-wise. For me it's definitely the CLI, package manager, and other devops around using the language that makes the context-switching tougher. npm vs gem vs pip and the fact that they all kinda work differently: npm will install libs into a "node_modules" folder in every project (so you could have 45 copies of React) where other package managers might install 1 copy system wide and your project just references it, so it affects how you deal with version mismatches. nvm vs rbenv vs venv/pyenv - slight nuances there too. Case in point try using Angular as a React dev. You're still in JavaScript, but the CLI part is different and more involved, the @ decorator syntax and other paradigms look/feel nothing like the React ecosystem. Getting into compiled languages there's usually a heavy IDE component you need to use and be good at (thinking of iOS/Xcode, or whatever C/C++ devs are using). But once I'm to the point of writing in a code file and I can easily run it and see my changes, I'm good at that point. Tips: LLMs are great translators. An LLM sidekick to accompany work outside your normal language or framework is extremely useful - can't recommend it enough. Not only will you get bespoke code examples but it will explain the "why" behind certain things that are foreign to you. And of course, just spend a lot of time coding in the language you want to make less mistakes in.