I hate this rule
As a general rule, if you need to improve a system by more than 3 orders of magnitude along some dimension, you're likely to have to rebuild it on top of a completely different technology stack altogether
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Raison d‘être for any tech startup.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Would be interested in hearing examples of this in practice. I agree in principle, but I lack the experience to think of an example of this off the top of my head
-
Good example: see blog post. “While historically Uber has been mostly a Node.js and Python shop, the Go language is becoming the language of choice for building many of Uber Engineering’s new services.”https://eng.uber.com/go-geofence/
- Show replies
New conversation -
-
-
What dimension would that be? If you refer to performance, I have seen 10x performance improvements without rewriting, but through optimisation.
-
10x is one order of magnitude only. 3 order of magnitude would be 1000x 1000x is not an easy task to achieve purely on optimization. It'll require scaling up and scaling out
- Show replies
New conversation -
-
-
I like the concept, not sure if I can quite agree though :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This assumes that the system already utilizes given resources fully and has minimized redundancy?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Could it also mean that the system wasn't optimally built in the first place? Tech stack is a moving target anyways.
-
Premature optimization is the root of all evil
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.