The value of keeping a daily worklog
I always keep a detailed worklog of real courseware projects and fun graphics projects. Good programming habit. A few years ago I started keeping a worklog for life in general, tracking sleep, dumps, moods, health stuff.
This morning I noticed a blister on the right heel that was starting to bleed. Seemed familiar, so I checked last year's life worklog. Yup, the same blister happened ON THE SAME DAY last year.
Last year I had been walking extra, avoiding one bus trip because I was having vestibular trouble that was sometimes tricky on buses.
This year I've been walking extra, avoiding one bus trip to minimize time under murder mask. I've also been adding a separate 2nd walk every day to burn off the annoyance, which I didn't do last year.
Patterns repeat, and there's a "reason" for the pattern each time. In reality the pattern matters more than the "reason".
Last year I reluctantly stopped the extra walking, took the bus both ways, and the blister healed in a few days.
Cold weather is also a factor in the exact date. Skin gets dry and stiff in cold, and shoes shrink a bit.
EXPERIENCE SURVIVES.... but only if you're able to learn from the experience. A worklog helps the learning.
Labels: constants and constants, coot-proofing, TMI