Thursday, June 23, 2005
posted by Simon at 1:37 PM. Permalink
Can you wait until then, or in the meantime, will you take some responsibility for your code and stop using such tools as a crutch to lean upon?
Firstly, using FxCop required by the company coding standards. Secondly, using such tools is taking responsibility for my code. Why search each of my lines of code for spelling mistakes when FxCop can do it for me? Why would I check each of my variables are pascalCased instead of CamelCased when FxCop can do it for me? Just these two things would save me a couple of hours, and there's so many more rules that FxCop checks for.The more time I can save by using tools to take care of the mundane (and therefore error-prone) aspects of coding, the more time I have to spend on the interesting and challenging bits.I am still new to programming, as I have only 10 years experience. Because of this, I am constantly looking for ways to get better at it, like reading books by experts, and also by finding ways to overcome some of my limitations. One of my limitations is that I'm not very good at remembering manual processes. There are two ways to get round this - one is to just get better at manual processes, and the other is to automate the manual processes so they don't need to be automated. Having read The Pragmatic Programmer, and the section on automating, I decided that automation was best for me. If I can set something up once, then it will always work correctly. I can't rely on myself to never ever make a mistake. And that's being responsible.
Thanks Simon for your blog post. I just encountered the same error and was rather dumbfounded, but some Googling came up with your post. Let's hope Microsoft provides a workaround soon; this is rather distracting for everybody trying to automate FxCop under Whidbey. It would help if it were clear under which conditions the error exactly surfaced...
Hi Jouni,I'm glad I could be of help - I posted it hoping it would be useful to somebody. I had a quick search with Google, and found nothing helpful. I intended to post a bug report, but found someone else had done already. I'm surprised Google didn't pick it up.I've found this occurs only when there are no warning s left, after fixing previous warnings. A great choice then: warnings or a crash!
Post a Comment
Create a Link
<< Home
