alt Hacker NewsI think codebases and optimizations are a lot like this.
A lot of people seem to think the way to make things work better and faster is to add elaborate caching layers and layers and retries and GPUs and multi threading and...
I find the opposite tends to be true. Make things fast and reliable by doing as little as possible. If an API is flakey, make it not flakey, don't cache the result and add a retry loop.
Replies
rootlocus • yesterday at 5:47 PM
"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."
~ Antoine de Saint-Exupéry
Start simple add the rest later when you needed it. How will you know you need it later? At 3AM. If it makes you feel better add a comment what will be needed when it breaks.
I see over and over wildly overdone code. When all I really wanted was some simple if conditions and a couple of loops. But that doesnt scale to XYZ per ns. Does it need to?
Boring wins almost every time.