When I look at the code of a website, I tend to expect a clean-looking sheet of html-tags and css-styles. Instead you mostly see unreadable code that is so hard to dive in that I give up almost instantly. Any example would be most of the sites fabricated by dreamweaver as Kroc pointed out. When looking at Kroc and theraje's code, you can almost immediately see the structure of the website through the html. Looking further into the css-sheets, you don't have to sift through one-line dreamweaver-creations but well-ordered and commented code.

And that is for me the most important part: I don't have any quirks against how you exactly order your code, if it's with the brackets on the next line, with many tabs, etc. As long as you can find the specific elements in a whip, it really doesn't matter to me.

I agree with Johann to match up the brackets, or with Jose Pedro Arvela, JJ and Glenn Friesen for the space-instead-of-tab quirk, but it does make the code easier to read. As I am learning myself html with Kroc's writing and w3schools, doing it old-school in notepad, my progress is much quicker when web-developers live to the thought of 'code is art', than 'if it works it's fine'.

I'm working on a website for a relative of mine, and I will probably share my experiences and the result with you all when it's ready, or when I'm completely stuck and need help from experts :)