TLDR · PROGRAMMING, DESIGN & DATA SCIENCE

YAGRI: YOU ARE GONNA READ IT

scottantipa.com2 min read

Summary from the TLDR newsletter

You shouldn't just store the minimum data required to satisfy the current product spec, you should also store data that you'll highly likely use, such as timestamps and contextual metadata. For example, instead of just deleting rows from a database, engineers should instead store data on who deleted it, how they deleted it, when, and why. While not every bit of data stored will end up serving a purpose, the extra data could end up saving you one day, which makes up for the cost of storing it. While you shouldn't log just everything, people rarely complain about a table having too many timestamps.