From 20937f27fa9b53f34d1ff278a3c0ce5b168e897e Mon Sep 17 00:00:00 2001 From: Tom Date: Thu, 6 Dec 2012 16:25:31 +0000 Subject: [PATCH] managing requirments is part of good design. They should be merged as it makes the document more terse --- README.textile | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/README.textile b/README.textile index 36cba9d..1f8d09f 100644 --- a/README.textile +++ b/README.textile @@ -85,18 +85,12 @@ h2. General ** Fix it if it ain't broke *** We only refactor code that we are actively working on, otherwise we live with the imperfections and tackle higher priority issues. -h2. Requirements - -* DO -** Ensure that acceptance criteria are clearly identified before starting work on a story -* CONSIDER -* AVOID -* DON'T h2. Design * DO ** Follow SOLID:http://en.wikipedia.org/wiki/SOLID_(object-oriented_design) design principles +** Ensure that acceptance criteria are clearly identified before starting work on a story * CONSIDER ** Pursuing a functional approach - immutable types, "pure functions":http://en.wikipedia.org/wiki/Pure_function etc ** Asking for a design review at any point of working on a story