4 ms·
If I were in that position, and wouldn't want to break off the relationship, I would probably try to change billable-hours to billable days (or even weeks?) I w
by a-saleh 8y ago
If I were in that position, and wouldn't want to break off the relationship, I would probably try to change billable-hours to billable days (or even weeks?) I would then try to keep strict 8-hour a day work-schedule (ok, maybe even just 6 to be honest :-)
Like, I am programming in professional fashion for around 10 years, and there are hours, where I make more progress than previous days. I don't want to be fighting for billable hours.
- balabaster 8y agoI've been programming since I was 8 years old. Professionally for the last 25 years. I've seen entire classes and subsets of programming paradigms dominate the industry and fade to irrelevance. There's enough to keep up with, without stressing about billing. I try to carry billable days or even work on retainer such that a minimum income is guaranteed and anything over and above is billed at a daily rate. From everything others have said, the jump from "programmer" to "consultant" is the hardest leap and one I've had considerable difficulty hurdling. My existing clients are often actively working against me to make this leap because they look at me as someone who can solve their problems in minutes and want them fixed now. It's on me to help change their mindset to one of allowing me to teach them to solve these problems for themselves. My greatest value is in teaching them to be self sufficient. It's helping them to become more than the sum of their parts so that when they call me, they're calling me to show them what they're doing wrong and show them how to fix it, I'm not fixing it for them.