I'm not exactly sure why, but programmers love architects. Sure, we lifted the design pattern concept from their work, but it goes beyond that. If you tell me you're job is that of software architect, or you're an architect of a project, I'll read that as you being at the top of the pyramid. You're the one who's in charge of the big picture, not cranking out lines of code day in and day out.
As I'm making my way through one architect's story, I've had a bit of a realization. Say an architect draws up the plans for a deck. When that drawing is complete, he doesn't have a high level vision for the deck. No, he effectively has the deck. Sure, there's the small implementation detail of needing a team to build out the deck per his specifications, but that's somewhat besides the point.
In my case, a computer executes my code, and in his case, a building crew. But at the end of the day, we're both creating something that essentially exists (at least as a complete specification) before it exists.
Perhaps programmers shouldn't be ascribing to being architects—architects should be ascribing to be programmers.
Thus ends my deep thought of the day.