@Lior: I think the 'divide' is, there are people who are or could be in the role of an architect, and people who couldn't. If you are a programmer who cares about the overall non-functional qualities of your system beyond your immediate use case, you're probably in the first group, and you think like an architect. You may not be in the role of architect in a given project, but you probably collaborate with one if it exists, or help the team to fulfill the role of an unexisting architect.
On the other hand, I know too many programmers who are not capable, or just don't care, about these concerns. These are the non-architect programmers.
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).