How to be a good Software Architect?

[Shaderhacker]

All:

I just got laid off because I wasn't a good coding architect compared to others in my group. I'm moving on to my next job and I have some time off to try and improve on both my coding skills and my design skills. The problem is, I have no idea how to begin. Going through a book on C++ only to forget most of it isn't really going to help much.

I was wondering what you guys suggest. I understand the basic concepts of the problems I am asked to solve but when it comes to architecting them into a solution using C++, I usually:

1) Choke and find it hard to even begin coding.
2) Type up something to get started only to find several holes and discrepancies in the software which ends up being rewritten over and over due to bad design.

Help!!

-M

[cshong]

If you ask me "How to be a good Software Architect?", I will answer like the following:

Applies to all position in a software development group

• Should look the satisfication of end users as the most important things. Don't care how you develop the software, it is useless if the end users do not satisfy with your software.
• Should always consider any suggestions or feedback given by the end users.
• Should not always thinking of $$$$$.
• Whatever you do for the software must for the sake of customers. (My emglish is not that good, if any grammar wrong, please forgive me.)

[Ejaz]

Google for "Design Patterns", this should occupy your free time and improve your design skills.