Add a comment

 

Re: Re-evaluating software architecture

Kevin, good comments. The things you mentioned (architecture, business analysis and program management) are all part of the every day activities that developers need to do. Good developers don't just write code all day long, they need to talk to customers, plan their work etc. Doing these things gives them an incredible amount of context and understanding about the business problem they are trying to solve. Moreover, I don't see a developer's job as being just 'coding' I see it as producing a solution to a business problem and a part of that will be to consider costs, service levels etc. The main theme that I see emerging is that the architect is responsible for more of the non-functional/technology selection decisions. I still don't see why this is different. Whether to use distributed or corrective transactions - isn't that a decision the development team should make, based on need? Are you looking for a single decision maker? Someone who has more experience? Do you think that teams don't understand the difference? I'm really not trying to be awkward, just trying to understand :) Thanks

Re: Re-evaluating software architecture


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).