This is something I can't really relate to. Sure you have a small "switching" period when you're jumping between languages but that's it basically. > 1. Try no

This is something I can't really relate to. Sure you have a small "switching" period when you're jumping between languages but that's it basically. > 1. Try not to use similar languages in the same niche. On the other hand I find it really simple to use similar languages, you don't even need to change how you think! It's just a change of syntax very similar to how I can switch between English and Swedish. The problem is when you want to use a language you haven't used in a while, but that too will mostly be a case of syntax issues ('How do I do X in Y'). > 2. Try to use one language at a time. I partially agree with this - it's easier to only use one language than switching and this is certainly the thing you should be focusing on if you're having problem with 'too many languages'. With that said I have never had a problem wih switching from say Perl to Javascript to SQL and back again in a short period of time. I find it easy to look at the surrounding code and just do the same. > 3. Keep notes and save sample code. I have yet to keep any notes for a specific language - I tried but never used it - but I do agree that cookbooks can be very useful. Otherwise reading code is always a great thing to do regardless.