E&C for C#, a bad idea? [yeah, right!]

Published Mon, Oct 18 2004 11:19 | girishb
According to John Robbins, E&C introduces more bugs because people dont really think the problem through and end up making mistakes that are not obvious to you when you are doing the debugging. I accept that. It probably does introduce many issues when you have not thought the issues through.
But, is it a bad idea? I don't this so. Using TDD will definitely reduce the need to debug often. But, when you do debug, these are times when you actually are pretty confident of the edits you would end up making since your tests would pick that up next time around.
E&C god send for: 1. Variable initialization /termination condition edits.
2. GUI edits
3. Prototyping
...
Oh, Lets not make it sound like only ex-VB folks are the ones who would have liked this. I am confident that there are many C#ers who are happy with this.
Anyone editing .NET code in VS.IDE would be happy about it. Everyone else, probably are just being masochistic.
[Listening to: Let's Get Away (Revised Edited Album Version/Old Hook) - T.I. - Trap Muzik (04:38)]

Comments

# girishb said on October 18, 2004 4:26 PM:

Yeah, it might be helpful for my two most common bugs: http://mikedimmick.blogspot.com/2004/04/two-most-common-bugs.html

The project I talk about in that link was a setup DLL for a Pocket PC CAB file written in C++, but even so...

# TrackBack said on October 19, 2004 4:28 AM:

John Robbin's take