Preparing the merge with Kim is quite some work, a lot of things have to be organized, bought,
made aware of a new address, so I’m quite busy at the moment. Arranging the “I’m finished studying”
makes it even worse, and I’m ending up with a giant TODO list with a lot of subcategories. I guess
just doing a couple of things every day, re-shuffling priorities and hoping that it doesn’t become
even longer is the way to handle is, yet I don’t see the light.
Organizing all that, I’m getting more and more aware that a lot of things are going to change in
the next two months. I’ll probably start working on a full-time basis, have to develop the feeling
that even when being half-conscious
that I’m not going to my old home (it’s quite some way off from the new one, so I’d better not).
I’ll have Kim around on a even-more-regular basis, be able to use my own kitchen, less annoyance by
ignorant people who happen to live right next door …
Ow, jumping on the APIDOX-bandwagon, I don’t have problems documenting my code, nor is it
something I don’t like to do. Dealing with API documentation, I walk through the code on a regular
base, cleaning things up, raising my own awareness of design issues, and adding documentation to the
interesting (==non-self-explaining) methods. The most interesting issue for me is what to document,
I think my own code is well-legible, and the method and class names are quite clear even without API
documents — yet documenting is still a good thing, to re-think choices made and to improve
readibility and understandability some more. Distracting myself from all the details I’m thinking
about while coding usually helps getting things done. Not at least I think that well-documented code
is even more beautiful and definitely adds quite some value.
Ow yeah, and due to moving houses, I’ll probably not have a “real” internet access at my new
house for a couple of weeks. Let’s hope one of our new neighbours “shares” an access point … >:-)