4 ms·
I consider myself a recovering perfectionist. It used to be that, all my code had to be perfectly understandable, all my variable names the perfect metaphor /
by iovrthoughtthis 9y ago
I consider myself a recovering perfectionist.
It used to be that, all my code had to be perfectly understandable, all my variable names the perfect metaphor / concept, my architectures the most scalable etc.
I found that the anxiety of having to make hundreds of correct decisions everyday left me exhausted. Ultimately it was not sustainable. I would agonised over tiny details for extended period of time.
I was eventually exposed to and much later internalised the idea that there are three types of decisions:
1. those you get right
2. Those you get wrong
3. Those you don't make
Anything is better than 3 in a non-life or death situation. If you're trying to learn 1 is not so important and doing 2 is the only way to truly learn.
- joelthelion 9y agoIt's a resource allocation problem. You've only got so many hours and energy in a day. I think the trick is to learn to recognize which code is more important and spend effort where it is needed. I think it would help if as a community we would recognize that sometimes writing crappy code is OK, as long as it's a conscious decision and.