There's a lot of stuff that's "Standard practice", "Conventional wisdom", or goes unchallenged because "We've always done it this way."* It rarely gets thoroughly tested to verify or refute, and it's hard to find the source.
Examples:
- Drink eight glasses of water a day.
- Being fat / having high BMI is bad for your health.
- 10,000 hours of practice to become an expert.
Another idea that refuses to go away is Waterfall Methodology for large software projects.
This paper by Winston W. Royce in 1970 said Waterfall is "risky and invites failure".
https://dl.acm.org/doi/10.5555/41765.41801
Thankyou @daedalus for the link.
As a Technical Writer, I find poor-quality documentation in Software Engineering a concern. And I worry when user-facing documentation is left to the end as an afterthought.
Winston Royce wrote:
At this point it is appropriate to raise the issue of - "how much documentation?" My own view is "quite a lot;" certainly more than most programmers, analysts, or program designers are willing to do if left to their own devices. The first rule of managing software development is ruthless enforcement of documentation requirements.
Attached images are from a Tech Writing lecture I've given to Software Engineers. See the ALT-text for more info. They look a lot like Royce's 1970 diagrams. Seems we Tech workers are doomed to repeat the mistakes of history.
#WaterfallModel #WaterfallMethodology #SoftwareEngineering
--
* Grace Hopper said it's "the most dangerous phrase in the language".