Ok, start with the "model" list below.
THEN do a little digging and reading:
199307 Engineering Times - Will High Technology Bring Engineering Disaster? [unverified software applied by unqualified users]
199409 Scientific American - Software's Chronic Crisis, W. Wayt Gibbs [software is being written but not by programmers]
199409 IEEE Spectrum - Judgment's Subtle Presence [replacing the decisions made by people with pre-programmed ignorance]
199703 IEEE Spectrum - Reflections on Complexity, Robert W. Lucky [just because you can does not mean you should]
199707 WIRED - Digital Obesity, Nicholas Negroponte ["personal computers" have never been people friendly]
199802 WIRED - Productivity Paradox [the numbers, folks, where are the numbers to back up the continued spending?]
199707 IEEE Institute - Software Engineering [accreditation of educational programs for "professional" programmers]
199800 Walking on Thin Ice by Peter de Jager [how the Y2K problem was created by the bureaucrats, not the programmers]
200004 US NRC - Digital Instrumenation Research Plan [the emperor has no software quality assurance program]
199907 US NRC- 464th ACRS - Commentary by Dr. Graham Wallis on RETRAN-3D [only "real professors" know what is correct way to "engineer"]
200502 US NRC ACRS Sub-C on THP - Commentary by Dr. Graham Wallis on TRACE [user manuals generally
** - DUH! so do most textbooks]
199907 No High Tech Training - The Financial Times by Rebecca Christie [a partial explanation of the productivity paradox]
200503 How computers make kids dumb - Andrew Orlowski - San Francisco [the title says it all]
COMPLEXITY and "FEATURES" for the pleasure and gratification of the purveyors of bloatware is NOT in the interest of the end users in any way, shape, manner, or form. (The "Engineer" in "Boson Engineer" might be a clue to "walking in my shoes".)
A simpler explanation: Hypercard, CricketGraph, Appleworks. With those three tools, and NO others needed, I was able to outperform, in quantity and quality, many of my peers in the "profession", for the simple reason that I knew what the limits of the tools I was prepared to learn were, and the added "fluffery" of "sound and fury", audio and craphic "effects", DID "signify NOTHING", when it came down to communication of useful information; why else is it called "information technology".
Don't get me wrong, I am well versed in the use of the "standard" business software, and I have found that the first thing I am asked to do for those whose expertise in nowhere as extensive as mine has HAD to become, is to TURN OFF as much of the "features" as is possible without hobbling the "standard" business software. The result being that I quickly demonstrate that, when properly applied, the previous pre-GUI versions of the software is more than adequate for the vast majority of users.
It is simply a matter of OVERALL increased "utility", if it is NOT there, it is NOT THERE!
A more technical issue is the use of human readable files; with the increased use of insanely complex file formats and compression techniques, the ability to do a "data dump" and examine the raw files is next to impossible (see for reference "The Forbin Project" regarding the "inter-system" language problem).
FLAME ON!