Yes, it happens to me too. If you want to get better at switching, practice more in both languages, separately. Most of all, don't worry about making simple m

Yes, it happens to me too. If you want to get better at switching, practice more in both languages, separately. Most of all, don't worry about making simple mistakes. If there's one thing that compilers, linters, test suites, and judiciously placed printf()/console.log() statements have taught me, is that I'm terrible at getting code exactly right the very first time. But that's OK, because if I've got the "shape" of the code mostly right (which I'm somewhat better at) then a couple of iterations on syntax, the order of expressions, and the fine details of those expressions, take very little time. Whether those fixups are needed due to language switching, or just general human error-propensity. Is your checked-in code quality, and your end-of-the-day productivity, on a par with that of the work colleagues you respect? If so, how you get there is working for you. If you want to get better at your craft, that's good. And spotting specific areas you'd like to improve at is helpful for that. But that doesn't mean you should beat yourself up for not being there yet.