waffle

I’m swamped at work and I feel like I’m torn between several projects in my free time.

I still believe that Rouse is a worthwhile project that could get done enough in the timeframe I had allocated for it if I had been able to use all of those slots. As it stands, it’s quite a bit along, but far from where I liked for it to have been. I’ll make sure to make the source available as soon as I can, no matter the disrepair in some parts (I’m being facetious, but I wouldn’t exactly release it either). I don’t want to block anyone who’s seriously interested in it from getting involved, and I don’t want my priorities, working schedule and/or inability to plan to be indicative that this project can’t be done.

As sometimes happens, writing here will be sporadic. I’ve actually got a lot of ideas, but they need time to mature and be typed out. I’m also pending a major WordPress upgrade and I’m thinking about taking advantage of that to do some, let’s say, well-overdue structural and other work. I dislike Twitter and Tumblr, but I also don’t have a good out-of-band source, and I have one post format. I once had several, and I might go back to that again.

And as for the software, I’ve got a few other new ideas and ways to rework at least two of the current involvements. ThisService in particular has been pending some Snow Leopard action for several months now, and I might finally have figured out exactly what to do about it, but that’ll take time to do, too. It occurs to me that I may not have stated this, but my goal is for, eventually, everything released under the guise of waffle software to be fully available under the BSD license (or even less restrictive).

All of this is not about a lack of interest. It’s too much interest. I’m spending far too much time context-swapping, starving the cores. I might need to give something away or up.

I want to be sure that what I do can be great. Making ten half-assed things instead of three good things won’t cause anything good, not even workload satisfaction.