3 ms·
And then you get an in-memory SQL database that is used for cached settings with a text-based SQL query to retrieve every configuration setting (thousands of ti
by tracker1 2y ago
And then you get an in-memory SQL database that is used for cached settings with a text-based SQL query to retrieve every configuration setting (thousands of times during a login) and have a login that takes many seconds to run.
Literal example... replaced with a lock-free hashmap, and reduced the blink of an eye in terms of time.
- xandrius 2y agoI don't see the problem here: the original dev delivers quickly, the next dev gets to solve an interesting problems and gets to show off how much time they saved.
- tracker1 2y agoThey could have used any hashmap or dictionary in the first place... The DB solution was far more complicated.
- gcarvalho 2y agoDelivering the over-complicated feature and improving the performance of the over-complicated feature both seem to get more praise than shipping the simple version to begin with.
- beeboobaa3 2y agoWho cares? Do you do your job for head pats or to actually get shit done?
- gcarvalho 2y agoTo make a living. Being acknowledged is good to keep at it, or so I heard.