Re:The not so hidden cost of sharing code between iOS and An...
by wpietri on Thursday August 15, 2019 @10:19AM
(#20705419)
Well, 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.
Re:The not so hidden cost of sharing code between iOS and An...
by eecc on Thursday August 15, 2019 @05:15PM
(#20709743)
Nah, 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.
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.