|A copy of a copy of a copy|
Eternal truth Josef
I pointed out to Josef that SItizens were inspired people, like Vikings going to Greenland.
Vikings are well loved everywhere now, but back then people hated Vikings, they had no TV show.
Josef offered a Mark Twain explanation, also likely plagiarized if Mr. Twain is to be believed.
Josef humbly pointed that any errors in my understanding were probably "transmission errors". (see GL-15)
The site Josef linked is long gone, but courtesy of the Wayback Machine, here are GL-1 through GL-16.
I especially like GL-7, programmers know it is still true today.
Glossary of Software Engineering and Management Terms
GL-1 Advanced design: Management doesn't understand it.
GL-2 All new: The software is not compatible with previous versions.
GL-3 Artificial Intelligence: Making computers behave like they do in movies.
GL-4 Breakthrough: It nearly worked on the first try.
GL-5 Capability maturity model: A method of determining to what extent the developer
can reasonably be blamed for the inevitable failure.
GL-6 Cleanroom: A management technique that applies to vertical interfaces
what the mushroom technique applies to horizontal interfaces.
GL-7 Compiler: A tool for adding an exciting amount of uncertainty to the size, speed
and correctness of a given program.
GL-8 Computer human interface: The means by which the program conditions the
user into never trying all the things that don't work.
GL-9 Cost modeling: A means of convincing the customer to pay for
whomever you need to keep employed this year.
GL-10 Customer: A primitive life form at the bottom of the food chain.
GL-11 Debugger: A tool that substitutes afterthought for forethought.
GL-12 Design: The activity of preparing for a design review.
GL-13 Design review: A process for ensuring you know exactly what it is you won't build.
GL-14 Design simplicity: It was developed on a shoestring budget.
GL-15 Disclaimer: Any errors in spelling, tact, or fact are transmission errors.
GL-16 Documentary hypothesis: The discredited notion that software is the
outcome of a systematic and rational process of development,
rather than the result of divine inspiration.