Ask HN: What small engineering habits compound the most over time?

I’m curious which small engineering habits people found disproportionately valuable over long periods of time.

Not major methodologies or frameworks, but smaller recurring practices that quietly improve effectiveness over years.

A similar vein, asking why in PRs. Most people don’t do the above, and asking why when it doesn’t make sense really helps understanding what your colleagues are actually thinking. Helps create a unified perspective on the codebase.