Jump to content



  • Please log in to reply
1 reply to this topic

#1 somersst


    New Member

  • Members
  • Pip
  • 1 posts

Posted 18 February 2010 - 06:52 AM

In the book they are speaking regulary about assumptions, and that they should be avoided. I don't see any concrete examples of this. Could anyone help me??

#2 Cadillacs57


    New Member

  • Members
  • Pip
  • 8 posts

Posted 06 September 2010 - 07:57 AM

wow, this is an old post, but im gonna reply to it anyways. when you assume that a functionality is gonna be this or that way, for example, you are ready to develop a functionality that plays video in a website and the websites owner can upload videos to be seen in the site, the problem is i code it for flv support, but the client loves AVI and i didnt ask him, i just assumed that the client wanted video and thats it, but the guy wants AVI, so i have to move from my allready developed flv player to the one the client wants or add functionality to convert avi to flv, but the point is that im sending the client the product they dont want.
the thing is like this
allways make sure that you are delivering the functionality the client wants

Edited by Cadillacs57, 06 September 2010 - 08:01 AM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users