4 ms·
Specification is hard because you are trying to predict a future state in a vacuum. You need to do that because creating the product is very expensive coding wi
by bob001 2mo ago
Specification is hard because you are trying to predict a future state in a vacuum. You need to do that because creating the product is very expensive coding wise. If instead you could instantly build to your current specification then you could iterate on the specification against a real product. Even if all that code is thrown out the end result would be a better specification.
- vladms 2mo agoFor some projects specification is also hard because of interdependence between modules or data or parts of the project. To which you might answer "make more tests". And we turn in circles, because it is hard to test something you did not thought of. My experience is that users (customers) even when presented with a prototype (done fast by AI, or previously, in the slow way) can take days to "discover" or "think" about things they wish. Then more days to understand why some wishes can't be done because it breaks other stuff they want. Maybe you have smarter, faster, more experienced and decided users. Then I can only say: good for you, you are lucky!