|Sent on:||Friday, October 4, 2013 6:46 PM|
On Oct 3, 2013, at 2:00 PM, Jonathan Vanasco wrote:workflow varies in each IDE by each team member. his/her friend might like pycharm, but that doesn't mean they will too.One thing you need to watch out for if everybody in the group uses different tools, is that the tools all get along at the level of whatever artifacts you are checking into your VCS.For example, we once had somebody in our group who used Eclipse. I couldn't care less that he used Eclipse and I used emacs, but his Eclipse would insist on reformatting whitespace, even on lines he hadn't changed. This led to bloated diffs on every one of his code commits.Where you sometimes run into problems with IDEs is when they require some private metadata which must be maintained along with the code to keep things working. As long as you don't run into cross-tool compatibility issues like that, sure, go ahead and let everybody use whatever tools they want. And if the tool that makes them happy (and more productive) costs $50 (or even $500), that's a pretty awesome ROI.
This message was sent by Roy Smith ([address removed]) from The New York Python Meetup Group.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about Roy Smith, visit his/her member profile