I love Resharper from JetBrains.
However, I am a bit torn in using it because I realize the double-edged sword it presents, and I think any fan of Resharper may agree with me on this one: while it may help you optimize your code on-the-fly as you are coding, over-reliance may weaken or even inhibit your learning of the code. This is especially true when you are under a tight deadline and don't have a lot of time to scour your code again for more in-depth optimization, but on the other hand, Resharper is there to save the day when you didn't know you could refactor your project a certain way, or use a certain technique.
To alleviate this conundrum, I try to take the time every time Resharper suggests and optimization (hello yellow light bulb) to learn the technique, and prevent the suggestion from ever appearing. As a junior developer I know this is especially important as I will not always be able to have Resharper available to me, and knowing these optimization techniques is key in everyday coding, however I am grateful that Resharper is there to suggest to me these techniques along the way, so that I may internalize them and use them in the future.
In sum, if using Resharper be wary not to rely on it too much as I believe it can inhibit and hinder actual code knowledge and optimization techniques if you don't take the time to realize what it is doing for you. On the other hand, you may learn a few new tricks you'd never known before and add them to your coding 'arsenal'.
No comments:
Post a Comment