I agree that consistency is important, but I think it's best that consistency extend to an entire team rather than being restricted to an individual coder.
A problem arrises when working on a team without a set standard. While each individual might have their preference and stick to it, they're usually working on a file that has been through many hands, so you'll have a mix of tabs and spaces. And the space people could have 4 or 8 column tabs. So you wind up with code that's supposed to be on the same level of indentation prefixed with 4 spaces, 8 spaces, or a tab.
I used to work at a place with defined coding standards - nothing passed review if it had the wrong bracket style, or if you had tabs instead of spaces, wrong variable naming format, etc. I thought it was rather draconian until I went to work for a place that had no standards whatsoever and saw what a mess things were. More that just aesthetic; it was diffictult to follow the code and figure things out when the indentation kept poping back in and out.
That all being said, I'm a space guy who converted from tabs. For one, a space is a space no matter where you view it. I've got my editor configured to insert four spaces whenever I press tab.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.