Reading the NATO report on software engineering that came out of the 1968 conference where the term "software crisis" was coined. (It's at https://www.scrummanager.com/files/nato1968e.pdf if you want to read it too.)
Currently on page 11. ELEVEN. (Out of 200+.) It says right here: "The need for feedback was stressed many times."
We knew. Have always known. Feedback is the key to everything. Any process that intentionally delays feedback is going to run into problems. We took such a wrong turn in the 1990s. Ugh.
=> More informations about this toot | More toots from testobsessed@ruby.social
Now reading Randell's 1979 comments on the 1968 report (https://dl.acm.org/doi/pdf/10.5555/800091.802915). He quotes J.W. Smith:
"I'm still bemused by the way they attempt to build software... They begin with planning specification, go through functional specifications, implementation specifications, etc., etc. If you look down the PERT-chart you discover that all the nodes on it up until the last one produce nothing but paper. It is unfortunately true that people confuse the menu with the meal."
(edited for brevity)
=> More informations about this toot | More toots from testobsessed@ruby.social
"Don't confuse the menu with the meal" is my new favorite phrase.
=> More informations about this toot | More toots from testobsessed@ruby.social
@testobsessed that's a variation of "the map is not the territory"
http://webseitz.fluxent.com/wiki/MapIsNotTheTerritory
=> More informations about this toot | More toots from billseitz@toolsforthought.social
text/gemini
This content has been proxied by September (3851b).