1:36, Friday March 5th, 2004 • feeling webmasterly • no comments
Working with a partner who is a hundred or so miles away is a new one on me. So far it's going well. We've been officially a team for about a month and he's picking knowledge up pretty damn quickly. This week we've been let down by general inertia on the part of one of my clients, by which I mean we've both kind of been sat on our arses, but that's no biggy. Next week should be fun though.
One of the big problems I have with my working methods is a failing in my ability to estimate task durations. It's something I've known about forever, and it's something that I've tried to fix before. I've certainly got better at it but I'm still not perfect. The fundamental problem is that I still believe I can just roll my eyes upwards and pluck a figure out of the air. The amount of times I do this is ridiculous. Even for whole projects sometimes. This does not work.
Previously it was a problem, but I got around it by working at the weekends. Working at the weekends is a bind but I got around it by slacking at other times and also by careful management of expectations. But now it's not just me that suffers when I make inaccurate estimates, it's Greg too. It's not fair for me to start costing him money.
phpCollab is a web-based project management system which I hope will the solution to this problem and ease the process of being a virtual team. It's based on Macromedia Sitespring, which is now dead. I evaluated Sitespring whilst working at Soup, but didn't really get it. Now I know a fuckload more about projects and business and all that and I really understand how useful this kind of tool would be. For me and Greg it's great, for a bigger organisation of more people I can see it would be practically indispensable.
phpCollab has projects and tasks and a calendar and lots of other stuff, but it's not a huge product. It's simple and straightforward and provides tools for making sure I've thought things through. For example, when I start a task I can enter my estimate for the task duration. I can then enter the actual time at the end and compare the two. I can compare the two across lots of tasks and projects as well, to get a handle on my slippage. At the moment I know the difference between my estimates and the actual time taken, but I have yet to aggregate that data into a useful report. phpCollab will do that.
phpCollab does lack a Wiki, which I think is a fantastically useful tool, simply because it's all things to all men. You can easily apply the power of hypertext to any structure or document. A user on the phpCollab message board had already had a go at hacking Wikki Tikki Tavi in as a phpCollab module, so I downloaded his release. I made a few more customisations just to make the Wiki fit visually with the rest of phpCollab and bang we're ready to go.
It's nice to have the combination of structured sections and a freeform melting pot, but I'd like the two to integrate and borrow from each other a bit more. I'd like to be able to use Wiki like formatting and linking in the rest of phpCollab. E.g. if I describe a project it would be nice to able to make a link to a previous project that was similar. phpCollab has envisaged the need for some of the links I would make, allowing notes, simple discussions and file uploads, but it can never codify them all. Neither should it, it would become bloated and much harder to use. A Wiki syntax for blocks of text (denoted by a Wikitext OK signifier of some kind) would allow people to build subtly on top of the current framework. This would also provide a way for the phpCollab developers to discover useful new features - people would already be using some kind of Wiki-based hack solution.
The hacking I did last night to integrate the Tavi Wiki was fun. I've often wanted to contribute to an open source project, but I'm no C hacker. I do know my PHP however, and I feel I've got something to offer here. I'd like to turn this into a proper project, to integrate a Wiki. I've just noticed that a Wikitext module has appeared in PEAR as well, although I think Tavi is a fine code base to integrate. I'm not sure if I'll do anything though, as I tend to go off the boil on things pretty quickly and I also have other projects that I would very, very much like to work on - the new Hype code base for example.
2:49, Friday February 27th, 2004 • feeling relaxed • no comments
I have a build process! I've been working on my own for so long I've never needed one before, but now I'm part of a team it's suddenly very much required. It's simple too. I edit the files, I try to compile them, when they work I check them into CVS. Then I have an Ant target which pulls the latest source from CVS and compiles it to the shared libs location for Tomcat. I then restart the server. All is full of love. Neat and it only took a day to setup! I've got CVS integration in Vim and a menu item that triggers the build through SSH.
Been messing about with irssi, which is definitely better than either ircII or BitchX. BitchX is the Emacs of IRC clients, funky and colourful though it is. Irssi is much more chill and is scriptable in Perl. I prefer the ircII scroll style of just letting text go off the top of the screen though. That way I can just scroll up with my wheel to see what's been going on. Then again it wouldn't be able to do it's funky windows business. It doesn't matter too much now I've worked out how to scroll up! In OS X, there is no meta key by default. There is an option in Terminal to use the option key though. Why the fuck this isn't turned on by default I don't know. I turned on a few other things as well, like terminal bell.
Using IRC and Irssi's Perl support has made me think lots about scripting and bots. Here is a quick rundown of the script ideas I've had in the last few days:
Bot to post to Hype
Bot to notify the #hypothetical channel when somebody posts to Hype
Bot to post here
Bot to allow posting to a Wiki
And some Irssi scripts using Mail::Glue, including:
Display current iTunes track
Interface with iCal, adding events.
Some of the thinking here is based around the idea that IRC can serve as a meeting place. The nice thing about IRC as a meeting place is that you can start prefixing things with slashes and you've got a rich interface to the outside world.
Say I was chatting to a business contact and we agreed to set up a real world meeting, I could use an Irssi script or a bot to record the date and time of that meeting. Personally I could switch to iCal on my desktop, but IRC would provide a centralised way for groups to co-ordinate and save to a shared server. This server could then pump out data to our GUI calendering clients.
Another example, I'm chatting and I need to make a note. A bot connected to a Wiki lets me shoot a note straight on to the end of a page.
These ideas center on one thing, that sometimes you need to just quickly make a sticky. IRC is a simple beast, with a shallow (but broad) interface system. Implementations of bots and scripts tend to provide a simple way of doing a straighforward task. If I want to post to a Wiki, why do I have to go through three page requests in a GUI, when I can set up my IRC client with defaults and then just post with a one line command. The flexibility and intuitivity of a GUI is lost, but speed is gained in it's place. And pretty colours. Pretty colours on black.
2:24, Wednesday February 18th, 2004 • feeling resigned • no comments
I unsubbed from www-style. it's really high volume at the moment with the 2.1 comments and stuff and it's all really boring.
Plus I realised that they don't really make the rules. They have done in the past, but now they seem more interested in writing specifications for concepts agreed in the browser-space (to some extent at least). Secondly, they never, ever, listened to my POV anyway. Oh well.
