So I have the odd bit of insomnia. You know, when you wake up at, say, 4am (like this morning), and you're instantly awake and thinking about stuff. Pondering. Planning. Designing
. That's the most difficult bit of awakeness for me.
and I used to do on-call support for Australia and New Zealand, so we have this --- I guess it's a "talent" --- of being instantly awake when you wake up at night. It's a bitch, it really really is.
So anyway, I have a tape diagnostic tool to maintain. It's all mine precious!
and it was born out of frustration with discovering that tape drives log information which they are not obliged to pass up to the kernel. I need to update it for some new tape drive models, add in some more pretty-printing, (re-)write the documentation, and generally make it ready to hand over to our Explorer team. Not that they're going to maintain it, but so that they can use it and [SGR
mode = "Potential Problem Analysis" submode = "Take Preventive Actions"] deal with the "if $developer gets hit by a bus" issue.
I also contribute code on a definitely ad-hoc basis to a crash dump analysis tool we have called Solaris Crash Analysis Tool
aka Solaris CAT
. My focus for this at the moment is on portability. Since Solaris is a multi-architecture operating environment, we greatly prefer to minimise the architecture-specific code. Especially since you can get almost exactly the same kernel issues on x86, x64 and sparc. Of course since I've been back from my holiday it's been a little bit of a numbers game with my day job and I'm going to have to wait for another few days before I can sync up my workspace and get back to the portability.
Then there's another tool I have in my head. It's still only at the planning stage, but it occupies my mind on my daily commute. It too is taking shape due to a lack of existing options.
I like coding because it's creative and helps me to solve problems. When I can't code I get frustrated. More later, when I've written some code