Is he saying a common source code control policy is a bad thing?I say unequivocally that both source code control and change management are absolutely vital. However using an IDE over the top of these tools can be problematic for a variety of reasons:
- How does one handle the sharing of code and modules between IDE projects when the common code is in the version repository. Unfortunately the answer depends on the combination of the IDE and Version control tool being used
- How to handle re-factoring? (re-factoring is a good BTW) Again the final answer depends on the combination of your IDE and version control tool.
- Is there an effective interface to your change management (ticket management) application/repository from your IDE?
- Depending on the tools and technology used IDE integrations to Change Management and Version Control systems can be fragile. It's an extra dependency to manage and support and not everyone wants to run a single solution from a single vendor.
powered by performancing firefox