rc3.org

Strong opinions, weakly held

IDE Project Files In Version Control – Yes or No? Of Course, Not!

IDE Project Files In Version Control – Yes or No? Of Course, Not!

Answering the age-old question. My short answer is, use the simplest approach that delivers consistent results given the tools used by the team. Keep in mind that at a certain team size, requiring people to use the same tools becomes counterproductive. Traditionally, that team size is 3.

3 Comments

  1. I disagree

  2. For me, requiring/dictating an IDE is Management by Pointy-Haired-Boss.

    I write code fastest in my own environment. I don’t need or want anyone to set it up for me or tell me how to do my job.

    A shop that has such policies does not need someone like me, and probably won’t see the value in my rate. On the other hand, I work fast, need minimal supervision and can figure out stuff on my own (or know to ask when I get stuck), and write quality code (in the right language for the job, be it Ruby, Java, R, PHP, Perl, Python, etc).

  3. Generally speaking, the most effective engineering organizations I’ve seen do not impose tool choices on developers.

Leave a Reply

Your email address will not be published.

*

© 2016 rc3.org

Theme by Anders NorenUp ↑