Comment by j on "How did you improve your coding skills?"

My strategies are quite simple.

I mainly work with people who I assume are better than myself.
I give talks about topics my current focus is on, so it forces me to actually do something about / think about it. For example next week at a meetup Errorhandling (hashnode.com/post/error-handling-in-general-cje2t…). I have to explain the problem, hence I force myself to abstract my thoughts to paper and back to a spoken form which forces me to rethink it several times. (scilearn.com/blog/how-students-learn-by-explainin…)
Read - apply - repeat. This is a quite obvious thing about a craft.
"Test thinking" this is mainly to isolate functionality. How can I test "this one thing"? Did I add to many dependencies? Can I extract it? Can I isolate it? Does it make sense to isolate it?
I try to visualize what actually is happening when I code.
If someone one else suggest a different solution I actually try to implement it (hashnode.com/post/how-would-you-write-the-followi…) so I can learn from them.
Separate the core functionality from the fluff.
Refactoring on regular basis, so I have to work with old code and thoughts to find a better way

Search Hashnode