3 ms·
As always, going too far either way is a bad idea. I've worked with "optimise everything ahead of time" people before and it can be an astonishing waste of time
by IanCal 10y ago
As always, going too far either way is a bad idea. I've worked with "optimise everything ahead of time" people before and it can be an astonishing waste of time.
You shouldn't completely ignore performance all the way through and assume you can sprinkle it on top later, but you shouldn't spend months squeezing the last few ms out of a feature that the client will change / remove when they try it anyway.
> Really, you are gonna refactor a 100k Java codebase to be fast when its done?
Maybe? Depends where the problems are. If the problems are huge architectural ones, no that sounds terrible. If the problem can be solved by later improving an inner loop somewhere and getting things solved then sure.
- mozumder 10y agoSpeed is user-experience. People used Instagram at first because it was fast. And they were quickly bought out for a billion.
- catshirt 10y agoI never heard someone say "I use instagram because it's fast"
- brianwawok 10y agoBut how many people don't X because it's slow? I don't browse on my phone's because ads make it too slow.
- deleted 10y ago[deleted]
- IanCal 10y agoSpeed is part of the user experience, but again it's more complex than that. Nobody would have used snapchat if it didn't take photos but the site loaded in 1ms. Nobody would use it if it had loads more features and took 2 hours. Speed is a part of it, and must be traded off with all the other parts of the user experience.
- deleted 10y ago[deleted]