3 ms·
I'll second the thanks - I've book marked this to add to our training regimes, some great tips. Some thoughts to add though (based on ROG's condesing). Whilst
by ErrantX 18y ago
I'll second the thanks - I've book marked this to add to our training regimes, some great tips.
Some thoughts to add though (based on ROG's condesing). Whilst I agree with "9 Write a comprehensive specification" in slide 14 he says "Development can be planned up front". By that I assume he means planning the process by which the specification is executed: or mapping how to build the spac. That's always a point I specifically avoid doing, at least till things are underway. One of the best things (possibly the only useful thing...) I was taught at school was that a specification is about what you want to achieve NOT how you plan to do it. Purely because if you plan out in too much detail how to execute a problem then you risk locking into an inelegant solution.
2 things I particularly like are the comments about "logged in logged out" (slide 32 onwards). One of the issues I often run into (and MUST learn to avoid) is beginning a design and framework in a logged out state and never consider the logged in state till I come to add it later. I often find this is much more of a problem with code than it is with visible design. Secondly "DONT reinvent the wheel" is the #1 bit of advice ever. Literally.
:)
- drewmclellan 18y agoBy "development can be planned up front" I mean on a really simple level. I think the example I gave in the presentation was that if you were implementing a user comments feature, you could reference the spec to find the other parts of the site/app that also need user comments and implement a single solution that will cover all cases. One of the downsides to agile is that you don't always know what's coming further down the road, so you either have to build extremely generic solutions (usually a waste) or very specific solutions that get adapted over time (refactoring is also wasteful). In situations where budget is tight - which is the position I was coming from - it is optimal to have solutions that are Just Generic Enough to cover needs. Thanks for your comments :)