3 ms·
> a good requirements spec I think that kills a lot of interesting projects right there. If I could write a solid spec, that would mean I believe I wouldn't le
by wpietri 7y ago
> a good requirements spec
I think that kills a lot of interesting projects right there. If I could write a solid spec, that would mean I believe I wouldn't learn much from shipping the product. And also that my competitors aren't learning or advancing.
- karmelapple 7y agoWhatever you first create has some kind of vision behind it. Even if that vision is a rough spec, it might be precisely the little bit of spec that’s necessary to get things started. A good requirements spec doesn’t mean it has to be heavyweight with all the corners and edges figured out. Instead, it can be just lightweight enough to get things moving in the proper direction... but some little direction is certainly needed.
- wpietri 7y agoNo, I've built entire products without a spec: http://williampietri.com/writing/2015/the-big-board/ http://williampietri.com/writing/2015/the-big-board/ It's fine.
- eecc 7y agoNobody says you have to write the spec beforehand. As long as you don’t blurt a lazy “use the source Luke” and take the effort to document and edit the spec during or right after implementing something, it’s ok.
- wpietri 7y agoWell, I think the comment I'm responding to expects the spec first. And almost anything that encourages writing a spec says to do it first. What's the point of writing the spec after? At best, it's duplicative. At worst, it diverges, making it incorrect.
- eecc 7y agoNah, it’s just this whole manichean polemic between two grotesque caricatures of processes; agile improvisation vs upfront waterfall planning à la nazi wehrmacht going to Russia. One just has to have an idea where to go before starting, and a good description where one went when you’re done.