4 ms·
Agree. Here is a rant from me expressing the same sentiment from a while ago https://jcooney.net/post/2008/06/08/Data-grids-lack-of-imagination-or-abdication-of
by josephcooney 10y ago
Agree. Here is a rant from me expressing the same sentiment from a while ago https://jcooney.net/post/2008/06/08/Data-grids-lack-of-imagination-or-abdication-of-design-responsibility.aspx https://jcooney.net/post/2008/06/08/Data-grids-lack-of-imagi...
- csours 10y agoYup, you see a very similar pattern with prototype or MVP code. People get fixated on the code or UI in front of them and they don't think about the actual use cases. http://www.snopes.com/weddings/newlywed/secret.asp http://www.snopes.com/weddings/newlywed/secret.asp
- flukus 10y agoI agree in general, datagrids usually mean "we have absolutely no idea what our users workflows are", but I'm not sure the credit risk example is a good one. If the credit risk is one of dozens of fields on a generic client edit table then it's awful. If it's a much more specific "adjust credit risk" form with relevant information to that specific workflow then it's fine.