Keep it DRY, Keep it Shy, and Tell the Other Guy..
Here is the original paper from Andy Hunt and Dave Thomas.
2004-05-20
2004-05-19
Operational - Reporting Databases
Martin Fowler's - Reporting Database
The separation of reporting database from the operational database provides unique advantages such as: data from business logic (calculated), a de-normalized view of database (fewer joins), maintainability of operational database and runtime performance (fewer locks)
See also:
* Martin Fowler Bliki
* Reporting from Database
The separation of reporting database from the operational database provides unique advantages such as: data from business logic (calculated), a de-normalized view of database (fewer joins), maintainability of operational database and runtime performance (fewer locks)
See also:
* Martin Fowler Bliki
* Reporting from Database
2004-05-17
Favorite links
Allen Bauer, Borland Delphi and C#Builder IDE Architect(http://homepages.borland.com/abauer/index.html)
Don Box's Spoutlet (http://www.gotdotnet.com/team/dbox/default.aspx)
Charlie Calvert (http://homepages.borland.com/ccalvert/index.htm)
Danny Thorpe, Delphi Compiler Architect (http://homepages.borland.com/dthorpe/blog/delphi/)
Steve Vinoski's Weblog (http://www.iona.com/blogs/vinoski/)
Don Box's Spoutlet (http://www.gotdotnet.com/team/dbox/default.aspx)
Charlie Calvert (http://homepages.borland.com/ccalvert/index.htm)
Danny Thorpe, Delphi Compiler Architect (http://homepages.borland.com/dthorpe/blog/delphi/)
Steve Vinoski's Weblog (http://www.iona.com/blogs/vinoski/)
2004-05-16
Hallmarks of a Good Design Review
* The reviewers are looking for issues in the design not on the designer.
* The reviewers and the designer should have the right attitude.
* A design engineer should accept criticism of his ideas and proposals by the reviewers.
* Distribute related artifacts to all reviewers before the actual review.
* The reviewers and the designer should have the right attitude.
* A design engineer should accept criticism of his ideas and proposals by the reviewers.
* Distribute related artifacts to all reviewers before the actual review.
The Principles of Lean Software Development
Eliminate waste by removing anything that does not add value - Create teams of people with specific responsibilities to enhance value.
Amplify learning by increasing feedback – Create weekly to monthly, full cycle iterations.
Keep your options open – Share, Organize direct collaboration, Absorb changes, Refactor, Automate test.
Deliver Fast – Enable a smooth, rapid flow in response to customer needs.
Empower the Team – Train the team to design its own process and make commitments.
Conceptual and Perceived Integrity – Test early, test often, test exhaustively and use an automated test suite.
Amplify learning by increasing feedback – Create weekly to monthly, full cycle iterations.
Keep your options open – Share, Organize direct collaboration, Absorb changes, Refactor, Automate test.
Deliver Fast – Enable a smooth, rapid flow in response to customer needs.
Empower the Team – Train the team to design its own process and make commitments.
Conceptual and Perceived Integrity – Test early, test often, test exhaustively and use an automated test suite.
Subscribe to:
Posts (Atom)