Rohit,

The language makes your intentions clear. Private is an unnecessary keyword. Any unnecessary ceremony is just that. As such, it should be treated lightly and removed because it does not add value.

Furthermore, these tips are for the MSpec framework. A framework which has no understanding of "private" so it's even more superfluous. The entire point of the framework is to remove language noise and focus on the essence of the specs.

With regards to the indentation, do you indent your method bodies to begin under the ()'s? In MSpec, these initializers are essentially methods, just reshaped. Removing the excess indentation treats them as such.

Sergey,

Wow. Garbage? Not having superfluous privates and indenting sanely is garbage? If you say so :)

169 is unused private. It's what makes the instance fields (It, Because, Establish, etc) gray, and it can give you a warning when building.

Sergey,

You have obviously completely missed both the point of this post and mspec. That is fine as mspec is a difficult thing to wrap your head around. This post is for people that use mspec and I am assuming you do not.  

With regard to underscores, no setting I have suggested forces you to use underscores in all your code. This is an mspec requirement. It has been proven time and time again that boxcar naming is much more suitable for longer sentence fragments than pascal.

Calling explicit modifiers "discipline" is just silly, especially considering resharper is set up by default to force you to use them. Replace the word explicit with redundant, which is what thy really are, and maybe you will see my point of view.

Spend some time in a language like ruby or any other with a high signal to noise ratio and you will find that your biases and predispositions are really baseless.

Again if you do not even use or see the need for mspec you can write this post off completely.    

Jason,

That's Damien Guard's Envy Code R:

damieng.com/.../envy-code-r-preview-7-coding-font-released

Beto,

It's called wombat:

dengmao.wordpress.com/.../vim-color-scheme-wombat

Of course it was adapted to VS, here's one such adaptation:

www.mohundro.com/.../MyAttemptAtConvertingTheVIMWombatThemeToSupportVisualStudio.aspx

KevDog,

Typing it is easy if you use an AHK script or something similar to replace spaces with underscores like this: blog.jpboodhoo.com/BDDAutoHotKeyScriptUpdateTake2.aspx

As for reading it, only you know what's easier to read for yourself. That said, I've seen a post or two on the subject in which the blogger quizzed his wife on which was easier for a long sentence and boxcar always won.

If you can learn to phase out the underscores while reading it's significantly easier to read. It also allows you to case things properly. I've yet to meet someone who has claimed they prefer PascalCasingThingAfterTheyHave given_boxcar_a_shot_for_a_while

And I love them!