Back in the saddle
Yesterday morning I switched back into working mode for unknown reasons. Decided to get stuff out of the way. Called the plumber to take care of a faucet that had started leaking, then immediately walked to the store instead of waiting for
'just the right time' as usual.
When I got back from the store, an email popped up .... which FINALLY gives me the instructions to start on the next version of courseware.
Almost always happens this way. I know when it's time to get back in the saddle.
Trite but true: Humans need work. Even 'retired' humans need work. This publisher's hurry-up-and-wait cycle gives a nice alternation between working periods and non-working periods, but the latest non-working period was too long. About 10 months since the last revision was finished.
Knowing that the next project would be difficult, and knowing that each month of delay would make it even more difficult, led to a buildup of tension. Without specific orders I couldn't do any specific preparation; I could only keep my programming skills sharp with
play-type projects.