3 ms·
I won't take a stab at answering your question directly, but I'll pose something to think about: It is the nature of many a developer to scoff at non-programme
by Waterluvian 4y ago
I won't take a stab at answering your question directly, but I'll pose something to think about:
It is the nature of many a developer to scoff at non-programmers running the world with supposedly nightmarish Excel sheets. And there is probably a lot of valid criticism.
But it works.
And any time I see Engineers trying to engineer things to their own taste, they just make things worse. You'll either make some portal with an inferior feature set or you'll reimplement a crappy Excel. Work with the Excel status quo, not against it. Don't look down at the problem from high atop a mountain, but rather admire just how incredibly effective Excel is as a swiss army programming tool that basically anyone in a business can use.
- thorin 4y agoI would agree with that, especially as the paying client will deliver the xls as the requirements and expect something that looks similar. It takes a lot of work to refactor the process and then build and design something that's familiar enough to be accepted but different enough to be an improvement. Have had to do this kind of thing many times. Where systems do win over spreadsheets is definitely in terms of data integrity, security and multi user experience so remember to sell the benefits and not just "look at the cool web experience / app we built".