2 ms·

There are reasonable lengths to dive, of which zero should not be a default case. The fact you're even aware that there's an alternative to choose means you're

There are reasonable lengths to dive, of which zero should not be a default case. The fact you're even aware that there's an alternative to choose means you're already slightly informed[1]. Being a bit more informed so that you know a solution will actually work is fine. I am not suggesting you shouldn't look at alternatives. I'm saying you should look at alternatives from the perspective of the solving the problem you have rather than arguing about pointless trivia that won't ever impact you or the app you're building (like row limits). [1] Every web dev who used nothing but MySQL for 15 years should be crying now.

zhte415 4y ago
> from the perspective of the solving the problem you have Completely. A small planning goes a long way, and helps define what problem is being solved. This is a particular peeve I have with lauding of pivoting. The plan didn't work out and you're now doing something else? That's great. At least something was gained and you're looking forward. But don't design for it. In other industries this goes by the perhaps less jargony terms salvage or wasteful production. But putting salvageable and waste in the description of a product solution doesn't sound as nice, and nor should it.