The essay project seems to be somewhat of a failure. This one has been over a year in the making: 2008-02-22, 2008-10-26, 2009-03-10.
Creating your own clock changes your relationship with time a little bit. The process of creating it changes things in yet more ways.
Once upon a time, I declared the The timeless world. That held for a while, in a sort of partially effective way that didn’t change too much since the first report. Then I invented my own clock. Suddenly it wasn’t dead numbers or confusing interpolation. Reading time was almost fun.
Of course part of being different enough to be fun is being, well, different. I very often don’t know what ‘time’ it is. I know it’s a little past dawn, almost lunch, or a couple hours to bed time. The things I actually use time for, without having to translate it to numbers in between. Occasionally I need to work with the outside world, at which point I do have to go through all that bothersome conversion; usually I find the position on the clock and switch back to visual mode from there on. One of these day’s I’d like to get some kind of event integration so I don’t have to do the conversion myself ;^)
A few months ago, I switched every clock I can to 24-hour time. A comment playing off the ambiguity of a time I had mentioned caught me in a problem solving mood, and I didn’t see any point in having such pointless ambiguity. It probably won’t be quite natural for some time, but at least I’ve started getting more accustomed.
The process of working with representations of time has finally explained something of the traditional system, and given me a little better understanding of what it all means. I suspect the standard 12 hour clock harkens back to the sundials. The top of the clock corresponds nicely to noon, and allowing a little fudge that changes throughout the year, 6-to-6 will cover the track of the sun, and most of the useful day, pretty well. On the other end of the day, 12 midnight is an anti-peak, operating in sort of a nighttime parallel image.
The Act Of Creation
There’s something about diving into a problem and forging into new (to you) territory. I often emerge with my own private language, superbly intuitive to me and utterly obtuse to everyone else. As a case in point, Disk Clock’s default 24/4/60/15 arrangement can’t hold a candle to the dominant 12/60/60.
Another interesting case was the dragon form in martial arts. As our school worked through the creation of our own forms, the yet to be created dragon form got remade as a sequencing of certain (large) set of multi-step techniques. During a break, I got stung with an idea for how to do this and put together the last 3/4 or so of the form on my own. During the course of the project. I had to fine tune and re-examine all the involved techniques in order to put them together smoothly. I actually came to the conclusion that the process – in part the act of creation – was as much or more valuable than the resulting form.
My instructor thought that form creation was something for very advanced martial artists, however. Funny thing is, as time went on and we worked with the process of transmitting this large, complicated form to the students, it was decided that it wasn’t working out very well. The replacement? Students design their own unrelated form from scratch, rather than in the semi-structured format I worked with.
When I began Disk Clock, I started working on it every chance I got. After a little while, this settled into a pattern of working on the weekends, packing up the two days work and making a release at the end of the weekend. I tried to get all the ‘other stuff’ done during the week. This actually worked out quite well for several months, despite occasional short iterations due to a martial arts seminar or other event.
But I’m actually writing this from a much later time. The martial arts test eventually blotted everything out – it didn’t matter what the schedule was, because I wasn’t working on anything. By the time it settled down again, I was post-1.0 and didn’t have an obvious successor project; certainly nothing amenable to short complete iterations. The result was somewhat wandering attention.
I tried to keep up the weekend schedule for the most part, but a string interruptions often caused me to try and ‘trade time’, programming on into the week. Of course, this cut into the amount of other stuff I got done during the week, and often ended up impacting the next weekend, causing the cycle to start over again.
One nice thing about this pattern is that little programming in the morning was a nice kickstart to the day. It was also nice to do something joyful before going to bed, rather than depressing things until I got so down I went to bed, depressed. So, I’ve swapped. I’m currently experimenting with a little coding every day, and dealing with other stuff during the day.
Ups and downs, of course. I miss being able to really pound on a problem. But I don’t miss getting stuck on a problem for long periods. I’m never stuck for a single long time, and often times the break gives me a new idea, or allows me to get comfortable with the concept of some drastic re-factoring instead of reluctantly staring at the code searching for a better way. Meanwhile, I need to try and maintain focus on other stuff for long periods of time, which isn’t always easy.