Ask HN: Taking a job you don't know how to finish yet

[darkotic]

You've been a developer for 20 years. As a contractor, you're excited about a potential clients upcoming projects. You haven't worked in this new space before. You aren't even sure you can do it yet. Do you jump in full-time and invoice for time spent learning? Do you learn first and take the job later?

[mckravchyk]

I think the biggest danger here is that you can severely underestimate the time needed to complete it, both in terms of the learning curve and of how much the project itself may be worth. The project may take 2x just because of the learning curve and needing to build scaffolding you would otherwise have, so unless it's super niche you may consider using a lower hourly rate to account for the learning curve - or don't, because you will probably underestimate it anyway.

I don't think I would do it without making a related side project first where there's no time pressure and can pause anytime - and I don't really care if it takes 300h or 900h because it's a side project. I don't even have to finish it.

[bckr]

Can you discuss this transparently with the client?

Can you charge for project instead of billable hours, or agree on a fixed number of hours up front? Would you be willing to work more hours than agreed on if you aren't making enough progress?

Are you willing to potentially fail?

[airbreather]

Definately you could up doing this twice, or three times to complete.

Not a problem if you get paid for all your time, rates rather than lump sum seem sensible here.