@Jeruba: “What did you learn, @tom_g? I’d really like to know.”
As a software developer, I am surrounded by people who crave change and innovation. It’s also the nature of the business. What we are learning right now will likely be obsolete in six months. Our work is really about perpetual learning, which is probably why most of us do what we do.
To get a glimpse into another mindset is interesting because a) it is so foreign, and b) I’m sure that this way of thinking is more common than I think (hence, the terrifying part).
And of course, not all change in software is good. And @Jeruba, you bring up a good point (and a common complaint developers have) about shipping “in beta.” There are all kinds of internal pressures within certain markets or companies to ship so fast as to deliver before it’s ready. This will happen. But I’m not sure software bugs are what much of this is about.
I get the feeling in this thread that the outsiders are under the impression that nearly all change is driven by “job security”, is unnecessary, provides no additional value, and that learning something new is too hard.
Let me use an example. Say you work for a city’s retirement board. All town employees contribute and are due a pension once they retire. The seemingly-simple world of municipal pensions are so complex that it requires a major piece of software to manage. Now, as a public employee working in a rather slow, conservative environment, you might feel that the software you are using to manage employees, their contributions, and their pension calculations is immune to market pressures (such as innovation/features/etc). But the pressures are there. First, there are the internals software pressures (language and framework versions, OS changes, db versions, etc). Second, there are legislation changes that directly alter the requirements of this software. This often requires changes from the database (how the data is stored) to reporting to UI changes. Third, the constant changes to the software can be so drastic over many years that a complete rewrite often becomes a necessity. Cars worked before air bags, unleaded gas, and other emission requirements. But if you are a car company, you need to change things – sometimes drastically.
Anyway, there is certainly bad UI design out there. But the existence of bad UI design is hardly sufficient in condemning the practice of UI design. Some of the best designers out there use eye tracking software and studies to see where users’ eyes go, and alter the content based on these guidelines. I suspect if you stepped back into the year 2000 to experience the internet and everything you do with it, you would be appalled. Change can be good, bad, necessary, or unnecessary. But change will happen. And it’s not always apparent to the layman/woman why these changes are happening.