Wednesday, August 15, 2007

How to become Technical Architect?

This is a broad topic. Surely. Anyway.. A short answer will be wisdom i.e. taking more interest on how solutions are built and meets the requirements which are beyond functional requirements and trying to meet the non-functional requirements like scalability, readability, maintainability etc.

Learning technologies: Its never sufficient. We will need to know different ways to solve the same problem. Can be Java, MS technologies etc.
Solution is important technology is not: From a business person there may be many ways to solve a given problem. As long as the solution gets done people are happy and thats why people need to take a look at different technologies constantly.
Learn building blocks: There will be many tools which are commercial and open source and depending on the cusotmers need: Time to Market or cost or both - technical architects can suggest tools which are useful. Build is NOT always the best solution.
Learn smart tools: Same work can be done by differnt people differently the main part is knowledge and usage of tools. This can be web spiders which help crawl the pages better.
Learn development methodologies: Different development methodologies like RUP, Agile etc are also important.

Future posts will take up different architectural problems and solutions using different techology set.

No comments: