Being part of an Architect Team...

So, being part of an architect team isn't as glamourus as one may think - building a foundation has to be solid from the get go. Many steps are put into place to help with this process.

First you have deal with functional requirements then technical requirements... Oh! and don't forget the reviews in between. Then finally the implementation and unit testing. The worst of all is the dreadful and gawd awful code review session that can drag on for days. In some cases you say to your self, "How in the heck did I let that slip through???". Finally-Finally, you get to go through the implementation and release it for everyone to use.

So you ask: How awful is this process? Imagine you have to write a program that will take 3 months to write but you spend 6 weeks up front figuring out what you're going to write, 4 weeks actually writing and another 2 weeks fixing you're code to fit within the guidelines of your company's common practices... That flip side would be to write and re-write the program until you hit the target of requirements and hope that when it's released to production it works.

Granted, I would much rather code for the whole 3 months but releasing a product to production and having it work with little or no hiccups the first time makes the whole process well worth it!

So I guess being part of the Architect Team isn't that bad after all...