Add a comment

 

Re: The frustrated architect

Maybe I should add that although I would prefer not go anywhere near writing 250 page docs, that's not to say I'm not able to do so if absolutely required to. In fact at every step I describe from functional specs, product backlog & project management/ScrumMaster to system design, code repositories, code reviews, coding & bug fixing, a good architect should have experience of doing all those things, & be able to do them well if required. Two consequences of that are that as an architect you have to be very choosy what you spend your time doing. Develop an archer's eye for picking the right problem & hitting it; secondly someone who is a solely book-trained architect who only draws & strategises away, isn't a tried and tested architect in my eyes: architects should have some battle stories. Analogously, a developer is a builder, a software architect is just as much town-planner as an architect of buildings.

Re: The frustrated architect


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).