Is it always OK to not explicitly initialize a value if you would only be setting it to its default value?
<p>Resharper just prompted me on this line of code:</p>

<pre><code>private static bool shouldWriteToDatabase = false;
</code></pre>

<p>indicating that I should not say " = false" because bools, apparently, <a href="http://msdn.microsoft.com/en-us/library/83fhsxwc.aspx">default to false in C#</a>. I've been programming in C# for over a year and a half and never knew that. I guess it just slipped through the cracks, but this leaves me wondering what's good practice.</p>

<p>Do I work on the assumption that default values are understood by all? This would result in cleaner code, but invites ambiguity if another programmer isn't aware of the default value.</p>
