Edit and Continue vs. Elvis
Continuing on a theme, today we talk about Elivs and E&C. We don't have a good way of measuring how Elvis uses E&C, since C# has never had the feature in a released product. So, what I say here is even more likely to be wrong than normal.
Elvis likes good code, but knows that by the end of the day he needs to have a working solution. E&C represents an opportunity to improve his efficiency and remove tedium. Elvis likes being productive, so he would welcome E&C.
Does he use E&C to experiement with a line of code until it works? Probably, but not often. Guessing isn't his style.
Does he use E&C alleviate long build times? Probably not, since the compiling C# is so much faster than C++.
Does he use E&C to compensate for complex bug repros? Yeah, sometimes. But C# apps tend to get the same functionality as C++ in fewer lines of code, so there's less complexity to manage. And the oldest C++ systems have been around a lot longer than the oldest C# systems, so maybe they haven't had an opportunity to grow quite as complex.
But given the choice between waiting for stop debugging + build + start + repro, and not waiting, the choice is obvious - you want E&C.
