Architecture Is For Everyone
•Télécharger en tant que KEY, PDF•
5 j'aime•1,325 vues
A gentle introduction to "architecture" presented at DrupalCon Paris, 2009. Intended for the casual and intermediate web developer interested in considering the bigger picture.
Recommandé
Contenu connexe
En vedette
Similaire à Architecture Is For Everyone
Similaire à Architecture Is For Everyone (20)
Plus de Jeff Eaton
Plus de Jeff Eaton (19)
Dernier
Dernier (20)
Architecture Is For Everyone
- 1. architecture is for everyone a gentle introduction to thinking big
- 4. who are you?
- 5. who are you? member of a dev team someone with client someone responsible for a site a module maintainer a core dev
- 6. who are you? member of a dev team someone with client someone responsible for a site a module maintainer a core dev frustrated!
- 9. Bahahahahahah. hahah. ahem.
- 10. “no devs” means “smart” code smart systems are complicated
- 13. • 7 stories (then 3) • 160 rooms • 20,500 gallons • 10,000 windows • 17 chimneys (maybe?) • Elevators! Central heat! Chaos and madness!
- 14. • 7 stories (then 3) • 160 rooms • 20,500 gallons • 10,000 windows • 17 chimneys (maybe?) • Elevators! Central heat! Chaos and madness!
- 15. • 7 stories (then 3) • 160 rooms • 20,500 gallons • 10,000 windows • 17 chimneys (maybe?) • Elevators! Central heat! Chaos and madness!
- 16. complexity requires a roadmap http://www.flickr.com/photos/47325272@N00/2541408630/
- 17. what makes an architect? no, seriously, what?
- 20. know the tools http://www.flickr.com/photos/thefangmonster/490423135
- 24. identify patterns http://www.flickr.com/photos/evaekeblad/916121820
- 25. identify patterns http://www.flickr.com/photos/evaekeblad/916121820
- 26. look around http://www.flickr.com/photos/gerlos/3119891607
- 27. building a site (architect style)
- 32. • Views, of course! • ImageAPI, ImageField... • Panels? Nodequeue? • Workflow! • Organic Groups! • And that’ll be custom...
- 33. WRONG!
- 34. GOALS
- 35. CONTEXT
- 36. PROCESS
- 37. ROAD
- 38. not as fun but now we have a plan.
- 39. but... drupal? road maps...?
- 40. YES
- 43. where are we now?
- 44. where are we now?
- 45. how do we reduce complexity?
Notes de l'éditeur
- Work with clients who need sustainable sites Training, Planning, and suffering
- Dries has talked about this for years Who here used to be a webmaster? You didn’t go away - you became a developer.
- “Eliminate the developer” - CCK, Views, Panels, OG, d7ux! I wrote “Using Drupal” - code free site recipes! Are we dying?
- More pieces than ever Pieces are bigger Nontrivial changes require deep understanding “No-code” requires knowing the code enough to avoid it
- Sarah Winchester’s mansion
- cool features. total chaos. no master plan.
- cool features. total chaos. no master plan.
- that’s software architecture.
- this is not canon, it’s fuzzy. What’s the difference between a dev and an architect?
- Too quick to jump to modules, features, “can we do X?” Need context: Winchester house was fine for its goal “Divide articles into pages!” break up long articles, or increase clicks? “We need a content staging server!” Or use workflow? OR NOT “We need X in core!” Do we?
- Balance Features, legacy code, performance, growth, real-world workflow, external environment (business AND tech), timelines, available resources we “know” many of these, but must be explicit
- the flip side: my grandfather was a machinist, and he hated architects. understand the details too, even if you delegate otherwise you’re just project manager, not an architect.
- If you only have one option, you’re doing it wrong Might be only one GOOD option Understand goals & constraints lets you get the spirit of the requests, not just the letter
- silos are good -- but only if they’re planned mismatched APIs in core overlapping modules, duplicated work, performance collisions in sites this is why architects love their diagrams
- Things you’re doing over and over (nodes, taxonomy, flag) Things you’re doing that others have (Pattern language) Christopher Alexander Patterns aren’t magic: they are lessons that have been learned
- "Use Wordpress." "Farm that out to an outside service." "Learn lessons from Movable Type's template system..." "How does the django team deal with scaling?" Don't have to become an expert at everything, but knowing how to learn from others - and get help from them - is critical.
- increase page views! more social features! escape $400,000 a year CMS! simplify editorial!
- Publication cycle? User participation levels? Traffic? Servers? Migrating newsroom to drupal, or just display? Legacy systems? Priorities? This is why specs are gold.
- How will we test? How will we launch/transition? How will we roll out new stuff AFTER launch? See the Economist presentation for a great example
- How are we going to get there? What portions are most important?
- Become wordpress? Become django? Facilitate distributions? Avoid commitment?
- Mostly volunteers Shared hosting Now Public (current client w/85,000 logged in users) PHP Language
- 100 fewer lines of PHP? 10,000 new sites? Code “feels better?” Ghosts leave us alone?
- Finding places where APIs collide Finding cruft of half-implemented features Eliminating things that are edge cases Adding pieces that are constantly re-implemented
- Not a code idea, but manifests in code Split APIs (fapi, dbtng, menus, hooks...) from “features” Push “features” to distros and profiles Plan silos, reduce assumptions, allow specialization