"Every age of the world has increased and still increase the real world, the happiness, the knowledge, and perhaps, the virtue of the human race." ~ Edward Gibbon (expired 1794)
A question to ask: Do you spend time (energy) debugging or shift your resources to writing new code? Sometimes it easier (or least faster) to rebuild that to fix what's broken.
I take the advice from others as prompts, but am careful when integrating new code. When I find myself debugging to appease others, I know to stop.
The coder reminds you:
Your time is limited. There's no need to fret about it all. You'll make it until you can't. You've got years of experience that proves you can handle whatever comes next. Worry without merit is wasted effort.
Improvement is hardwired into my code. I know there's always room for improvement, but am keen to avoid the trap of unobtainable perfection. The paradox of improvement is that it can never be obtained.
Systematic improvement can be integrated into any program. It's a matter of following a process. Here's one I recommend, and there are plenty more to explore.
It's important to keep an accurate log. Be mindful not to compare yourself to others and maintain an objective viewpoint to the best of your ability.
CANI: Constant and Never-ending Improvement
II: Incremental Improvement
This is a recurring theme in most self-help books these days. It can achieved by asking yourself this simple question:
What could I do today, that I would do today, that when accomplished, might make today slightly better than yesterday?
Can you apply this to YOURSELF?
What could I do today, that I would do today, that in doing so would make me better than I was yesterday?
Systematic improvement.
My program contains an ongoing improvement routine. CANI is the acronym for Constant and Never Ending Improvement. I learned it in my twenties from Tony Robbins and it still resonates today, some 30 years later.