I don't think there's a real need for it, although if you all use the same tool you can help each other and give tips and tricks. However, people have their own tools and preferences and I always like it when employers take my individual needs into account. One thing to watch out for is licensing. GitKraken, for example, has a free tier for open source development, but it's not for professional teams. A developer may not care about that a lot and I think you can just download and use it, but your company is legally obliged to buy a license*. If everyone uses their own tools, make sure they get the appropriate licenses. And that's where another pro to all using the same tool comes in... Managing licenses is a hell of a lot easier :D * Although the chances of getting caught/fined may be very low. Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript

Just like my saves, early and often. ;)

Do you mean compile or actually test? A function that adds a and a instead of a and b compiles fine, but it's still a bug. I compile more often than test. How often I compile depends on what I'm doing. If I'm writing new functionality I usually don't compile until I think it's (partly) done. Whenever I'm fixing bugs or typo's I sometimes compile after every few keystrokes. And I save VERY often, like every minute or so (and sometimes more often). Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly