> So designs are going to change. Why not take the approach of “let’s see how I can adapt to this”?
Because there's huge costs for everyone involved...?
"let’s see how I can adapt to this”... Across how many devices? If a school lab updates, but I don't... I know have to learn something new when it's probably not necessary. If I update, and the school lab didn't... will my stuff be compatible? If I send a document to 'version Y', will I still be able to use it in my own local previous 'version X'?
If I'm a business, how do I support X changes across multiple customer bases? And for how long? I have support people to train to answer every stupid question from people who can't find ABC menu item any more because it's now rendered as 'abc' in a different menu area.
In MANY cases, there are compounded, massive costs to seemingly small/trivial/design changes.
Because there's huge costs for everyone involved...?
"let’s see how I can adapt to this”... Across how many devices? If a school lab updates, but I don't... I know have to learn something new when it's probably not necessary. If I update, and the school lab didn't... will my stuff be compatible? If I send a document to 'version Y', will I still be able to use it in my own local previous 'version X'?
If I'm a business, how do I support X changes across multiple customer bases? And for how long? I have support people to train to answer every stupid question from people who can't find ABC menu item any more because it's now rendered as 'abc' in a different menu area.
In MANY cases, there are compounded, massive costs to seemingly small/trivial/design changes.