Re:Ben Nadel: Only Solve One Problem at a Time
by arise on Thursday November 10, 2022 @02:40PM
(#33551960)
A notable historical example was NASA's "all-up" decision to launch all stages of the Saturn V on the first test:
https://appel.nasa.gov/2010/02/25/ao_1-7_f_snapshot-html/
“In retrospect it is clear that without all-up testing the first manned lunar landing could not have taken place as early as 1969,” von Braun wrote. “It sounded reckless, but George Mueller’s reasoning was impeccable.”
Re:Ben Nadel: Only Solve One Problem at a Time
by d4mi3n on Thursday November 10, 2022 @02:51PM
(#33552156)
I think this may be a misattribution of what soaks up time: is it the change itself or the friction of the process of making that change?
e.g. code changes are easy but merging and build procedures take a log of time, encouraging larger batches of concurrent work.
I think it depends on the situation, what the best approach is. Is it a system, which is running in production and you are operating an "open heart"? Well, better only change one thing and check. Is is a newly developed thing, which you develop on your own dev machine? You can easily fix many things and many more will still remain for further iterations.