＋设为首页 ＋添加到收藏夹
in the past, ive written in broad terms about flip, the fusebox lifecycle process, a methodology for delivering successful software projects that work (despite its name) with any - or no - software framework. in this article, i want to "drill down" on one aspect of flip and see how it is used in practice.
a central tenet of flips philosophy is the recognition that users really cant tell us what they want until they see it. if that sounds paradoxical, consider how often youve delivered a project youve worked long and hard on, only to hear the most dangerous words that can come out of a clients mouth: "you know what would be nice..."
what comes next is a litany of client wishes and needs, followed by the sound of the developer muttering, "why didnt they tell me this before i built it?" the reason clients dont tell us what they want is that they cant. they have no vocabulary to even think in those terms. attempts to remedy this using such things as flowcharts and uml diagrams are mostly unsuccessful; clients simply dont think in such structured ways. instead, they react to what they see, leading to the familiar "you know what would be nice" recitation of wants.
as frustrating as this seems, it can be argued that its really good news as it provides us with the opportunity - if we accept it - to act not merely as coders, but as developers. coders are charged wit... 下一页