Earlier quoted context omitted.
> People regularly make costly mistakes in shipping and receiving, purchasing and manufacturing because they have to deal with shitty confusing applications that look just like that screenshot. Currently unscrewing one of those as my day job. "Delete all production orders for period" - no confirmation, no ability to rollback (beyond me restoring from a backup) that kind of thing. It's not that it isn't user friendly,…
> "Delete all production orders for period" Hah! I built one of those once! The (very abbreviated) conversation went something like this: "I need a way to bulk delete orders." "Umm... Are you sure? I can't think of a good reason to delete a bunch of orders in production." "Yes. We absolutely need this." "Ok..." A short time later "Why does it ask me to confirm? Just make it do it." "Sure..." A week later, after resto…
The out sourced developers however...very much yes I can.
Half the things do the wrong thing wrong, the other half is the wrong thing sorta working.
There was clearly no attempt to understand what the user wanted or any attempt to ask the simple questions like "Why do you want X, is X related to Y, would it be handy to pull in related Y for display X" beyond the terrible code quality (and database architecture, I wish I was kidding when I say it took 49 to 69s to search for a quote (I timed it on repeated runs), it now takes ~400-600ms and I still think that's too slow (and I search more things) there is just a complete lack of any thought/effort or consistency.
Even the tables aren't consistent across the system - sometimes click a row opens the related entity (with no indication that's what it does), sometimes there is a "view" button in the row on the right, sometimes on the left.
It's just pile after pile of UX disasters/architecture code disasters, no wonder the original lead dev came close to a nervous breakdown, I just don't think he was capable of dealing with a system of this complexity.