This seems like a very interesting book. How relevant is it for people starting consulting businesses, i.e. not solo freelancers but rather freelance companies?
I'm talking about questions like: how to allocate the different people to different tasks, how/when to hire employees, hiring on-site employees vs. hiring freelancers who work from home (potentially form elance or similar), etc. Does this book get into any of these topics at all?
Hi - I wrote the book and its focus is on client work as an individual, rather than starting a company. In future releases, my list includes adding a section on sharing work with others, which might be more relevant. If you ping an email to feedback@freelancedeveloperbook.com with stuff you'll like covered, I'll add it to my Trello board
Great - I've sent the email, hope it helps. Will definitely be picking up this book.
By the way, I've heard the book "Design is a Job" praised on HN as a freelance Designer's guide to freelancing. I'm currently reading it. It seems your book is very similar in its goals and content, only for programmers instead of designers. If I'm right, I would definitely consider marketing it as "Design is a Job - for developers", or at least include that message somewhere on the leanpub page. I know I looked for it.
Thanks, too, for the suggestion. I've tried not to make my pitch copy on the leanpub site too SEO-ey, but I certainly get the point about helping people understand what the book may be like compared to ones they know. I'll check out "Design is a Job" when I get a moment.
I'm talking about questions like: how to allocate the different people to different tasks, how/when to hire employees, hiring on-site employees vs. hiring freelancers who work from home (potentially form elance or similar), etc. Does this book get into any of these topics at all?