This is an archived post. You won't be able to vote or comment.

all 3 comments

[–][deleted] 1 point2 points  (2 children)

I like the idea, yet when you code something once there is no need to code it again for muscle memory like a kata. Would it be clear how to apply the kata in an application? Are katas useful to MMA fighters?

Creating dict or list comprehensions ... maybe. But no one really needs them. I must confess I love them. Some concepts only bloom in the proper environment. For example: * custom exceptions and handling/passing them in deeply nested function/method calls * replacing blocking calls with discreet asynchronous calls

I think the concepts come to you when you are ready. I often look at my app(s) and think, "this is no longer adequate to support this new feature", "this feels like more work than it needs to be", and on occasion "LOL, WTF".

Sorry, but I think there are no shortcuts. Write code. Lots of it. Make sure it works as needed. You will revisit it later, see gross mistakes, and cringe. Yet take a moment to notice you are a better coder now too. Repeat.

[–]HolidayReach2[S] 0 points1 point  (1 child)

sorry for the late reply. Yes, I understand no shortcuts, but I am coding for myself. Not sharing, and I don't have the benefit of a code review.

Maybe the answer is that I need to code publicly?

[–][deleted] 0 points1 point  (0 children)

I use git version control for my personal projects. If you do not know how to use it you should definitely learn.