I hope I never have to inherit any of these scripts. It isn't exactly 'self documenting' to have nested commented code blocks that sometimes should run and other times should not run.
For all the clever that went into manually comment in/out of code, you could probably have written a proper IF block. ex: IF !EXISTS(/* check for table */) begin /* create table, populate with data, etc. */ end <-- now instead of commenting, you can simply run & rerun the script without a comment block to explain when the comment block should or should not be [un]commented
If you have any more dynamic manual craziness, don't stop at a clever commenting process: make it a working Stored Procedure. I don't have time to learn this 'convention' for commenting and manually running code. (who does?)
That said, if you are talking about the process of developing/testing ad-hoc code that is en-route to becoming a real procedure... then thanks for the insight into your methodology. I feel like it is a bit too complicated for me to remember and use naturally.
btw, thanks for writing the article too.