i feel also with time, you get better from recovering from these stupid mistakes faster and also come up with better solutions/fixes faster.
This will have taken your younger self , twice or more to understand the problem and come up with solution
This will have taken your younger self , twice or more to understand the problem and come up with solution
Last Friday learned that Postgres (and apparently MySQL) will effectively ignore an index in a column when combining “ORDER BY … LIMIT …” and “WHERE some_column IN some_array”. I had introduced a query that timed out on a critical prod table , fixed it by removing the limit, and turned it into a teaching moment to others who could have made the same mistake: https://stackoverflow.com/questions/8909163/avoid-full-table...