Live Draft :: From Design Practice to Code Trackhost: James Coplien, Senior Agile Coach, Nordija
- Dont make your prototype very good (or else you’ll get a “Ship it” command!)
- Use a non scalable toy technology that will force you to throw it away
- Architecture and coding are products of design, there is no verb as “Architect”
- A GUI is NOT and interface between the user and the software, it rather depicts the structure of the program
- Extracting objets from use cases do not work
- Example: An account is often not an object in banking systems!
- Instead, direct maniplulation
- Architecture is important in an agile processs, and some of it should be done since the beginning
- Don’t be driven by technologyin designing you model (driven oop)
- Usability is coming from domain exprets for domain design
- Models (MVC) tie different domains to reflect user’s workflow and bussiness composition
- After a well defined domains architecture it is about a SMAP (simple matter of programming)
Architecture of reusable systems, and it is exactly the MVC
- Good architecture can result in a good team organization which can result less meetings, and better standalone teams
- It is about objects not classes
- Thinking in objects brings reusability, thinking in classes is about your own nerd!
Can you explain more please regrding the following points:
1-Dont make your prototype very good
2-Models (MVC) tie different domains to reflect user’s workflow and bussiness composition
3-Use a non scalable toy technology that will force you to throw it away
Comment by badi — March 24, 2007 @ 12:47 pm