3 ms·
Signing off on interactions has usually been an iterative process and so on most projects there's a bit of frog boiling going on. The logarithmic increase in s
by hinkley 4y ago
Signing off on interactions has usually been an iterative process and so on most projects there's a bit of frog boiling going on.
The logarithmic increase in set/insert times as your user base swells by orders of magnitude, for instance. This was all fine when we had 100 test users in our database. Response time is not so great with 100k. The first app I ever did performance tuning on essentially had time series data and (when I got there) quadratic search time with 2 criteria. Nobody before me had bothered putting a year's worth of data into the sample data, let alone 5. They also hadn't dreamed of 3 search criteria (surprise, cubic time!) Of course before me the app was too slow to care - literally could watch the UI paint it was so slow.
When you have two buttons on the interface everything is snappy. Each new button should reasonably expect logarithmic overhead, decent designs often add square root overhead (memory costs on real hardware are n^0.5), and bad designs add constant or quadratic overhead, and either nobody checks or is so focused on the deadline that they can't see the project burning down around them. Every day that click takes a few milliseconds longer.