Yes. Especially applications. App people have absolutely no idea about how to solve a computing problem for the general timesharing public user. Thus, a fix to underlying software that works for them is likely to break every other business' computing usage outside of their box.
When this happens at the OS level, things can become more complicated becaues the "fix" is based on the local work load and computer usage. These fixes could shut down another site's system.
I can guarantee you that anybody who works exclusively on one flavor of computing doesn't have any notion of how computers are used outside of that box. The reason bit gods become gods is because they acquire the ability to be able to imagine system usages they have never encountered.
Timesharing operating systems make this kind of thinking a prerequisite of its developers, maintainers, designers, marketers, and everyone else who does any work to get the OS distributed. The one reason Mipoo is poo is precisely this lack of thinking.
snip That may be, and I'm not claiming otherwise. What I'm talking about here is not specific technical knowledge, but .... It's two things. One is some...
Work flows are the day to day actions every person took that affected a product's manufacture and distribution. There are times when I include the work flows of the people who have done tasks so that the bit gods didn't have to "waste" their time shooting dinner or emptying their wastebaskets.
In TOPS-10 lingo, you were SOUPing.
Sigh! Accumulating bitrot is a disk that has been trashed. I don't seem to be able to say this and get people to understand.