Re:Haskell, Ada, C++: An Experiment in Prototyping Productiv...
by nickpsecurity on Friday April 05, 2019 @08:33AM
(#19581856)
Most evidence I've seen supports it. This is especially true when people start integrating stuff with or building on top of a deliverable. Even more if that stuff was designed with the deliverables good and bad behavior in mind. It becomes a legacy system that sticks around. Knocking out its problems ahead of time can have considerable savings. Plus, a benefit not often mentioned is that knocking problems out at design time is easier since everything is fresh in developers' minds. They just wrote it.
Now, it might not apply in an environment where everything is designed to be pluggable and easy to change without breaks. Maybe folks should run some new studies on such projects to see if there's any major benefits for up-front investments in quality. Enough to pay off that up-front investment like in the other projects.
Re:Haskell, Ada, C++: An Experiment in Prototyping Productiv...
by ajxs on Friday April 05, 2019 @06:55AM
(#19581346)
I didn't really look at the quote as being a literal, canonical truth. I have my own doubts about it being _literally_ true, but I feel that the underlying idea that "the longer a bug persists through the development process the costlier it becomes to fix" is true.
Re:Haskell, Ada, C++: An Experiment in Prototyping Productiv...
by nickpsecurity on Sunday April 07, 2019 @09:07PM
(#19601121)
Reposting it on Lobsters, hwayne had a nice counterpoint to it:
https://lobste.rs/s/6ywivn/are_delayed_issues_harder_resolve...
Anyone that studied what TSP was supposed to do would get what he was talking about. It might be supporting that TSP's up-front and lifecycle efforts make late changes in lifecycle easier rather than that non-TSP projects can easily make late changes.
see eg https://news.ycombinator.com/item?id=15216407