3 ms·
Yeah, I think the problem is that we’ve been taught that pre-optimization is the root of all evil and that we should getting it working before improving upon it
by samtho 3y ago
Yeah, I think the problem is that we’ve been taught that pre-optimization is the root of all evil and that we should getting it working before improving upon it.
Pre-optimization became a thing because enthusiasts liked the challenge of creating an elegant solution, but I posit that it continued because devs knew they were not going to be getting back to fixing inefficient code if it mostly worked. Usually stuff like this doesn’t matter when you’re leaking 5mb an hour on a 128gb dedicated server and you’re deploying at least twice per week. But when the devices that connect to you go from 10,000 to 1,000,000, you’re leaking 500mb an hour and then you have a problem very quickly.
- eschneider 3y agoWhat I'm thinking of isn't so much 'optimization' as basic design decisions. For a lot of IoT products that integrate machine learning/computer vision features, you've got a choice of implementing that stuff in the cloud or on device. You need a bit more compute to do the work on device, but ongoing costs are far lower and a lot more predictable. As a side effect, you also enable fully independent operation.