It does teach you about effort and pragmatic productivity, which is a general skill.
I've spent years trying to design code that would give me some benefits but in reality they were taking too much time for low use-case value. When you have time pressure, you write code very differently. You aim at the smallest patch that can solidly implement a feature. It minimizes code changes, patch size, bug introduction, time spent, client happiness. Also mentally beneficial to see tiny regular results.
It does teach you about effort and pragmatic productivity, which is a general skill.
I've spent years trying to design code that would give me some benefits but in reality they were taking too much time for low use-case value. When you have time pressure, you write code very differently. You aim at the smallest patch that can solidly implement a feature. It minimizes code changes, patch size, bug introduction, time spent, client happiness. Also mentally beneficial to see tiny regular results.
I argue that those things are a different skillset and don't have overlap with the previous examples.
Strange, to me its obvious. When you have to be tight you learn to be tight, you aim for faster, leaner operations.