I do largely prefer the hourly rate myself. The reason is that it is way too easy to work 'more' but it is very hard to work 'less' when paid daily. It was a problem I had for all the years I was employed, and I hate it..

With the hourly rate, I can just go off at lunchtime if I feel like the weather is good, and plonk in 12h on the following day if I like. And nobody /minds/ because they know I'm on an hourly rate. Also, I have a 'primary' client, so I can work there in the morning, and take on another contract from home and work that in the afternoon for example. I've been doing that a lot lately, and yes some days you end up doing silly hours, but they are all /paid/ hours.

I used to charge (as a freelance) on 'project' and 'phases' and so on, but very often, you always end up working more due to shifting specifications, bugs etc. By sticking to an hourly rate, you remove that constrain, and if you are 'expensive' companies will try not to waste your time -- while I see a lot of 'daylies' being given menial jobs because they are considered 'cheap' and expendables.

> But it sounds like you're doing much smaller chunks of stuff for multiple clients? I tend to dedicate myself to one client at a time and work more or less full time on one project. Serial monogamy one might call it... I'm not an employee because I work on a project basis and then leave with no fuss :) I'm definitely a contractor, are you more of a freelancer?

It's mostly one client at the moment, but not full time (10 days a month) and often based around when a new dataset becomes available to analyse. I work in Biotech and not strictly software development, so it's a slightly different model I guess.

It's also partly my fault, sometimes life gets in the way or I run out of steam after 4 or 5 hours staring at a dataset.

For contracting I'd ideally like to have a few clients and move between projects.