Even in failure, an increase in understanding is a win
When what we're trying to accomplish fails, the extra knowledge and clarity we get just by making the attempt is a win all by itself.
What is the point of points?
Points aren't hours, but they sorta represent hours. Or do they? 🤔 If you're as perplexed as I used to be, here's a few thoughts about points.
Time and mental energy are limited resources - use them wisely
Learning, creating, and improving are all constants in software development. There's no reason to ever be bored in this field! But we do need to be careful about what commands our time and energy, because those are limited resources.
Enjoying the wins, accepting the losses
When our code isn't clicking, negativity can quickly overshadow all the positive. That's when we need to remember our victories!
What's taking so long? (a question every dev gets.. and even asks themselves)
Ever solved a problem, just to beat yourself up on how long it took? Me too. Maybe we need to spend more time making the invisible.. visible.
Beware the bite of the refactor bug
Refactoring code is part of the dev life, and can even help keep the code healthy, but going too far can do more harm than good. Ever after a decade of writing code, I still have to remind myself from time to time!
Sunk costs, timeboxing, and asking for help
One of the biggest struggles I have with programming is knowing when to ask for help. A little struggle is necessary for growth, but when am I just wasting time when I could be learning from others?