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
@testobsessed Would you say that this crisis is still ongoing? When I was working on my thesis, about 15 years ago, my TA said it was. When I entered the industry and later was able to look left and right, it definitely still looked like it to me. Having moved companies a few times now, I can see a few glimmers of hope, but my view is very limited. Would you mind sharing your take and experience on it?
=> More informations about this toot | More toots from georgberky@chaos.social
@georgberky Jerry Weinberg wrote: "It may look like a crisis, but itβs only the end of an illusion." (Secrets of Consulting)
In that spirit, I don't think there ever was a crisis. Not really. Rather, I think a lot of folks held tight to illusions. They still do.
So. 2 big questions:
=> More informations about this toot | More toots from testobsessed@ruby.social
@testobsessed Thank you ππ». People seem to cling to them when disillusionment forces change upon them that is unpleasant π€. Was "we can plan software development start to finish line" one of them? Or maybe even "software has a finish line"? I'm beginning to strongly doubt the latter.
=> More informations about this toot | More toots from georgberky@chaos.social This content has been proxied by September (3851b).Proxy Information
text/gemini