Unquiet

I’m going to have a demo of __Clutter__ up this weekend. I’ve been so busy with other responsibilities that I haven’t so much as looked at the code in two weeks (not to mention that updated lighttpd portfile I’d been promising. I just received an update patch that I’ll be integrating tomorrow morning.

Part of the problem I’m experiencing with __Clutter__ is that I’m doing this work for me, not for a client. Clients have set expectations and requirements, and I can develop to those standards and those deadlines without a problem. In the past that’s meant I spent a lot of extra hours working as the deadline loomed, but I’ve still never had a problem developing for a client.

When I’m coding (or writing, or what-have-you) for my own purposes, however, I reach a certain point where I’ve coded myself into a corner. Almost always, this mistake arises from my desire to add new features as well as a lack of clarity about what I really want from the application. I reach a point where the complexity of the work becomes more than what I intended… my incredibly usable idea has become just another one of the many half-usable applications out there - and that’s not what I want.

So this weekend: the final rewrite of the __Clutter__ core, and then something for the public to see and comment on. Either that, or I abandon the project and move on to something simpler for the time being.