Using Resharper - is this a "personal solution"?

Question

My team recommends ReSharper to all developers, but he doesn’t "apply" this recommendation. As a result, whenever I open some kind of code, it immediately pops up to me whether the developer who wrote it used ReSharper or not. Tell-Tale characters are an unnecessary attachment, the use of redundant type declarations and general parameters, typos in symbol names (because it would be difficult for them to fix them), etc.

An unstated assumption seems to be that a ReSharper user is a "personal decision" that does not affect anyone else. But is this really so? What is the ideal enforcement level on this issue?

Answer 1

If you work in a group, then nothing that affects your code is a purely personal decision.

Answer 2

  <Opinion> 

I think the use of tools like ReSharper should be defined in the same way that style conventions are implemented. Everyone does it. Or nobody does it.

This is very annoying, because the developer has hundreds of warnings from other developers who simply did not write to the same standards as everyone else.

  </Opinion> 

Answer 3

You must write code that complies with the coding standards agreed by your team (something like this is enough). Your choice of VS plugins, key bindings, colors and font sizes should remain yours.

I wouldn’t work too hard on the minutes, such as "over-type ads." More importantly, people should be aboard with SOLID principles.

Answer 4

After using R # for more than 2 years, I sympathize with you. I believe that my code is significantly cleaner, more patient and more readable. And my standards, both for my own code and for the code that I have to review / maintain from others, have made a quantum leap up. However, the fundamental rule of politics (human nature in fact) is that most people resist change ... and imposing them on them never reduces this resistance, so persuasion is always the best approach ...

Answer 5

I think the tools should be used by the whole team to be effective.

Having said that the “problem” you are facing is a code quality problem and is not related to R #. The errors that you describe can be created with or without R #, and they can be avoided by checking the code or pair programming.

R # helps to write good code faster, and I can’t come up with a developer who doesn’t want to improve its performance, so if you want everyone in your team to be able to use R #, convince them that they will use it more. Again, pair programming is a goidd way to demonstrate the merits of a new tool.

Answer 6

Personally, I believe that standards in a team work best if they are enforceable and enforceable with a tool. Resharper does a good job (assuming you set the same rules) to give file warnings for formatting differences. Rules only matter if there is a tool that applies them, whether it's Resharper warnings or something else not so important.

My current team is about one and a half. I use R # like the other members, but some of our team just use VS without it. Nevertheless, we are doing our best to ensure that we all comply with the standards provided by StyleCop, so R # users are happy (provided that we have StyleCop installed for Resharper), and non-resident users can work fine.

Answer 7

It is best to use a consistent set of rules in a team / project, regardless of how they are applied (using the CA tool or code reviews, etc.).

In the absence of a clear standard at this point, you need to relax so that your rules (or resharper's) are accepted by what other programmers do, even if they do not fit your personal style. In fact, programmers are all people, and you will never find two such people who do the same thing - some flexibility is required.

CA tools often provide an opportunity to spend time (most of the suggestions are pretty rubbish in my experience). I mean, if all the members of your team can effectively read, understand and maintain a piece of code as written, then often there is little refactoring in this code - be careful, wasting time trying to satisfy Resharper, when you make changes, there will be really make no difference to the readability, maintainability, reliability, portability or effectiveness of your code. Turn off these warnings, and do not waste time refactoring the code.

Having said that, you should definitely campaign and promote CA in your team and your manager. The team / project will benefit and everyone will benefit from the use of CA tools.

Answer 8

Using the code refactoring tool is not a problem for me. Think about it - you yourself do not write code, you write it for others. Architects must make their plans accurate, readable, and understandable because they know that someone else is behind them. They have tools that help them do this. Why don't programmers do the same? We complain that this is “too much work” or “Why fix what works”? The truth is that not refactoring comes down to pure laziness.