How many times as a developer do we get asked by our clients to create a new story to implement a feature assessed by the client as “trivial”? How many times do we get surprised by their reactions when we give them our story estimate. I’ve seen developers give this sort of optimistic estimate too, without considering all the wrinkles, like error handling, alternative usage scenarios, abusive usage & security concerns, and all sorts of other issues that can be way bigger than the “happy-path” through the code. Here’s a neat little article from Brent Simmons that summarises the sort of user experience and technical design that has to go into the “Oh, it’s easy” feature.
Data
Meta
-
Recently
Calendar
Archives
- July 2010 (2)
- June 2010 (2)
- May 2010 (1)
- April 2010 (2)
- March 2010 (1)
- February 2010 (1)
- December 2009 (2)
- November 2009 (2)
- October 2009 (2)
- September 2009 (3)
- August 2009 (4)
- July 2009 (3)
- June 2009 (5)
- May 2009 (6)
- April 2009 (6)
- March 2009 (10)
- February 2009 (13)
- January 2009 (13)
Categories
- rants (15)
- technical (77)
- architecture (26)
- business (18)
- professional practice (32)
- programming (32)
- tools and techniques (18)
Tags
agile apple business code composition craftsmanship ejb emergent design framework glassfish hibernate java jpa jsr168 library linux macintosh management maven methodology money mysql oo opensource oracle osx patterns persistence poorly attempted humour portal profession refactor rewrite scrum spring Sun svn tapestry5 test driven design test first tools unix weblogic wizards considered harmful xpprogramming
scot mcphee