(no title)
bdunn | 11 years ago
Figure out WHY a project's being commissioned and then propose what your clients actually care about (hint: not code), vs. doing the usual "here's a proposal with a bunch of technical line items, a quote, timeline, and a signature field"
logicallee|11 years ago
What I'm saying is that it is not quite fair to assume that every 'freelance programmer' (OP or your readers) can do that to the extent that you can. Business requirements analysis is simply a different skill from programming.
Consider the example where the person buying your services is on to your pricing strategy, and misrepresents the value of the business downward (or hides it from you), so that you are left only with the process but no good idea of the value of it.
Can you still do your business analysis, and price it as you suggest? Not nearly as well. Even though as far as code goes, you could still write all of it.
So I would say that what you advocate goes well beyond the idea of a freelance programmer, to include aspects of a business consultant. (Finally, really good proof of this is that in some cases you may well be able to hand off the actual coding to someone who will follow your instructions at a low hourly rate. The fact that this is even a possibility suggests that the value you're describing and capturing may not be in the specific programming at all, but a different layer entirely.)
tptacek|11 years ago
This isn't theoretical. Lots of people on HN execute this strategy successfully.
djloche|11 years ago