General information
Title:
Why break what's not broke
Environment versions
Network:
Windows 2008 Server
This is in no way meant to be a reflection on the change in the UT interface, but it brings up a topic about changing something just for the sake of being different. If somethtng is working great, why make a dramatic change to the interface that even experienced user's have to search through to figure out? I constantly see this in new versions of software.
In my personal software develpment I always attempt to upgrade to new helpful features, but I usually don't make it so different that it requires a lot of thinking on those who have used the software for years. Am I one of the few who think this way, or is the industry moving so fast we feel compelled to make something different just to make it seem more modern or just different - often times at the expense of productivity?
Just wondering......
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only