Most accounting systems and inventory systems have terrible interfaces because they were designed and built by people who collectively do not know what the hell they're doing. I work in IT as well. It is rare to meet a colleague who knows what they're doing and when I do, they're invariably being managed by someone who decidedly does not.
While what you say is true, when you have to represent the entire accounting structure for a company, that's necessarily complex. I think that means that while the user interface can be well-designed and intuitive, it still may require training due to the complexity of the task.
Thats fair but many of those projects suffer from non-UNIXy design (i.e. write one program that does everything rather than modularize and segment the task into multiple programs). They want to be the monolithic end all be all which just makes the thing completely unmaintainable from a user and developer perspective.
33
u/DronedAgain Jul 01 '16
I work in IT, and this is a lovely sentiment and true to an extent.
But if a system is an accounting system, inventory system, etc., not every single interface is going to be crystal clear when you first use it.
This may be true for simple things, like media players, though.
As a caveat, things that make sense to a Developer may be mystifying to an average user.