5 ms·
> The first time you encounter something, you're probably going to make some mistakes. There's a post going around tonight about how someone forgot to put an in
by matsemann 5y ago
> The first time you encounter something, you're probably going to make some mistakes. There's a post going around tonight about how someone forgot to put an index on some database thing and wound up doing full table scans (or something like that).
Which post is referenced here?
I also believe this to be a tooling issue. It's often opaque what ends up being run after I've done something in some framework (java jpa, django queries whatever). How many queries (is it n+1 issues at bay?), how the queries will behave etc. Locally with little data everything is fine, until it blows up in production. But you may not even notice it blowing up in production, because that relies on someone having instrumented the db and push logs+alarms somewhere. So it's easy to remain clueless.
- claytonjy 5y agoPretty sure it's this one https://news.ycombinator.com/item?id=29132572 https://news.ycombinator.com/item?id=29132572