I probably shouldn't have left it at that - if there's much regularity outside of tables, then you're definitely doing something wrong. Within code I see the al

I probably shouldn't have left it at that - if there's much regularity outside of tables, then you're definitely doing something wrong. Within code I see the alignment as a way of highlighting regular areas as potential spots for refactoring. Sometimes it doesn't make sense to turn something into another layer of abstraction yet, but it may later. I can certainly see how the extra spacing might grate on some people's nerve's, though. Edit: Something I hadn't thought of - you mention "rivers of space" - aligning code might make it harder to read for coders with dyslexia: http://uxmovement.com/content/6-surprising-bad-practices-that-hurt-dyslexic-users http://uxmovement.com/content/6-surprising-bad-practices-tha... Regarding your point about unsigned types - If I'm remembering correctly, "Writing Solid Code" had a section about exactly that - nasty bugs caused by things like looping over unsigned integers in reverse.