I consider it’s important to measure our progress, so how could we measure our progress on:
- Daily task or exercises?
- At the end of the 30-day challenge?
I consider it’s important to measure our progress, so how could we measure our progress on:
My work quite often consists of facing a huge existing mess to make it suck less.
Here are typical signs that I consider to be progress in right direction:
If you’re working on the same code base all month, maybe keep a tally of how many times you go “huh?” in a day. With any luck, that should plot a nice downwards graph.
I’d say it depends pretty strongly on the task itself. Something like increasing code coverage has a very direct metric that it can be measured with, but something like an updated README doesn’t. I would say this might shape the form of tasks we take on specifically for this reason, as a task that cannot easily be measured is a bit more tough to do. Some metrics I can think of:
Can you please clarify this question?
Do you mean your success or failure at the entire challenge, a specific exercise, or more generally?
Friend I also didn’t understand your question