I think hourly vs fixed vs weekly vs value billing involves a lot of personal preference, as well as depending on the project and the client. We'd all be doing

I think hourly vs fixed vs weekly vs value billing involves a lot of personal preference, as well as depending on the project and the client. We'd all be doing it the same way if there was one best way. Most of the discussion tends to be centered around profit, but there's other factors e.g. weekly billing sounds good for being booked up but you'll have less freedom over your day-to-day schedule, hourly can be good for unpredictable/flexible work but you'll probably have to keep more fine-grained timesheets (which is a drag, and are awkward when you have to explain why things got held up from some inevitable tech/code problem), fixed/value based projects with large budgets can be high pressure when things aren't going as planned. Then from a client perspective, a non-technical client is probably going to be more comfortable with a fixed price, and tech clients are going to be more understanding with daily/sprint based charging as they'll know how unpredictable coding can be. It's interesting how for salaried work compared to contracting work, the way people are paid is standardised and there's usually little negotiation power there for choices.