Sunday, 15 May 2011

How to encourage positive developer behavior with an IDE? -


IDE's goal is to increase productivity, they do a great job on it, refactoring, navigation, inline documentation, auto completion productivity Is to increase.

But: Every device is a weapon Very IDE helps in producing chunk codes. There is an invitation to create a Bud Code for some INDE features: Code Generation, Code Formatting Tools, Refactoring Tools.

The IDE tries to isolate the developers with the most important information necessary. It is a good thing that you can start working. But at some point in your career, you have to find out how to start the process. You can ignore this description for a while, In the end, they are important for writing working products (vs bolt together that works 90% of the time).

How do you encourage the behavior of other developers working with IDE? This is a question that is old as a copy and paste.

To get the right effect: Developers can use their maximum creativity and inspiration IDEs and all related tools because they look fit. Nobody should take strict measures against them. I do not want anyone to demotivate and force anyone to be encouraging good behavior. If you do wrong, then he should suck it a bit. You can ignore it in the same line as the "acceptable rate" metric (and reputation), but life is better if you follow the rules .

(Should work in a particular setting. You can ignore reviews, change staffing or more education possible solutions.)

Train your IDE instead of being trained by it.

The way you (or your team) wants, formatting the code. Disable the heck, even in those cases where it is understood that I have a sensible combination of such an IDE tab and empty space (where \ t is clearly tab character) Something is not aligned:

  {\ tcout & lt; & Lt; "Hello" \ t & lt; & Lt; (Some + tall + expression + \ t to_produce_the_word (world)) \ t & lt; & Lt; Endl; }  

In languages ​​like Java, you can not escape boilerplate. You have the best option to see the generated code, to make sure it's written with your hand. Modify it as needed, if possible, configure your IDE to generate the exact code. Eclipse is very good on this.


No comments:

Post a Comment