Sorry to slightly deviate from the actual question, but I have been following a couple of recent questions by the poster whose main ambition is to become a successful architect, which is very good.
One wont become a successful architect by just reading books. And there is no single book which can be called a bible (even more so in the context of architecture).
I had exactly similar questions like you and Here's the thing I learnt. Hands-on experience is the only way to become a successful architect. All the rest of the books should be only be used a reference (based on the platform you are working).
So what next.. Get away from the programmer/developer position and take-up an architect's job ( if not senior , atleast a junior role).
Like many other's said, in real world an architect does only 50 to 60% of a real architect role, the rest is soft skills.
Hope that helps.
WHAT is your favorite color? Blue, no yellow, ahhhhhhh! Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop