A new year
Had a quiet New Year's Eve at home. Had a slightly less quiet New Year's Day at a party put on by my neighbours. Filipino food is nummy.
I have been incredibly lax on the code front lately. It just doesn't seem to be something I enjoy as much as I used to. I'm still (inactively) following Parrot and a couple of other projects, but code of my own just isn't getting done.
That being said, I deleted all of my half-done projects from last year. There were almost thirty of them. I can't say I'm sad to see them go -- they will no doubt be replaced by thirty or so half-done projects come a year from now.
Having read the most recent article and comments on the trust metric, I am reminded that the whole point of the certifications is lost on some people. I'm happy with the certifications I've received, as each and every one is right on target (depending on who you ask, I'm either an observer or apprentice -- certainly nothing higher at this point).
I have given some thought as to the matter of certification aging, and I think that certs should degrade with age. If I write a couple thousand lines of code that is used all over the open source world but proceed to do nothing for the next two years, am I a one-hit master, or am I an observer who did that cool hack? My thinking is that the latter is more correct.
In terms of keeping the general public informed about what one is/has been up to, that is the responsibility of the individual. If I don't want to claim credit for something, I don't have to -- but I certainly can't expect the community to acknowledge me for whatever I won't acknowledge myself.
I'm rapidly forgetting my point, so I'll just leave it for now...