"Pragmatic Architecture"
Demystifying architecture. What is an architect? That person who gets paid more than everybody else and has management fooled? "Architect" == Latin for "cannot code anymore"?
Infrastructure architect, enterprise architect, systems architect.
An architect's areas of concern/decision-making: communication, presentation, state management, processing, resource management, tools.
A higher-level perspective than implementers typically think at.
Addresses the high-level decisions that are really, really difficult to refactor (e.g., changing from WinForms to a web app is not a "refactor").
This stuff seems less frightening this way.
My problem is a lack of vocabulary: patterns, libraries, the specifics. I learn the abstract concepts, the "rules", the grammar a lot more easily. (Linguistics vs. language... the same reason I can't speak more than a few words of French, Russian, Spanish or German today but can describe broad commonalities and differences among them...)
Swag update: cozy p&p summit polar fleece vest.
Day 2 update: "Architecture is that stuff that if you don't do it right, it costs too much to fix."
A good target for stories is not that you can't think of any more to add, but that there's nothing you can take away.
"What do you do with troublesome senior devs who won't cooperate with agile methodologies and can't get along and get in the way of the team?" "Make 'em architects!" [audience LOL. pause.] "Hmm, seriously, that might work."
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment