Hacker News Reader

Comment by parksy | Hacker News Reader

Like I say, I made the mistake in signing the contract. In my case there was no "15 days late", it was payment on completion, and to the letter of the agreement the work wasn't complete until they said it was. Definitely do things different these days.

Edit to add - as per your experience the team themselves were pretty good to work with but in my case they had no sway (or at least said they didn't) with whatever archaic nested babushka-esque financial and legal mechanisms this century-old institute had. Perhaps if I'd put my foot down and refused to work it would have forced a proper renegotiation and worked out better in the end but it was a constant state of "we'll be finished next week, just one more thing" so the old sunk cost fallacy was always in deadlock with pragmatism and the frog slowly boiled.

View on HN

What do you do differently nowadays? How do you stop this happening

Me, my problem has always been eagerness to please, so I'd agree to "just do it" and skip the first part.

Don't, under any circumstances, do that.

If the client asks for a fixed price, then don't propose an implementation cost. Instead, propose a discovery cost. I can easily say how long I'll need to figure out what needs to be done and deliver a documented solution with an estimate of the work needed.

If they refuse this approach, then the only other option is "time and materials", i.e. I will send you a log each week of the hours I've worked and the product I've delivered, and you will pay me each week.

If they refuse discovery as well as time and materials, and insist on fixed price, then I walk away.

Don't do fixed priced work.

It can be difficult to find work that pay per hour but almost impossible to find fixed price work that does not result in at least some feeling of being exploited. And I would only do fixed price work again if: a) The deliverables are commoditized and I own the codebase; b) I am desperate.

I think there is a conflict of interest at the root of fixed price jobs. You are incentivised to provide as little as possible within that fixed price and the customer is incentivised to extract as much as possible.

Yes which's aggravated by many times the client having unrealistic expectations. It's a race to the bottom.

Isn't it quite obvious, don't do stupid contracts.

As a contractor/freelancer you can do any kind of contracts. You can commit to free work for whole year if you want (or are stupid enough to sign a contract that requires you to work for free).

With normal employment there are lots of laws that protect you so you don't have to think about your contractual duties. Just turn up and do what is told and you will get paid. When you do contracting it is quite different game.

Pretty much this. It was a stupid mistake and it cost me dearly. My choices were to suffer and work for a few dollars a day, or suffer even more and be blacklisted in my local community, if not being dragged through the unknown depths of some legal dispute that I had no recourse to fight. And to be fair, I agreed to do it, so it was kind of on me for not doing my homework. We live and learn to protect ourselves, but when there's a glut of people who haven't learned yet it's very lucrative for people who will exploit ignorance deliberately.

You spend some time reading /r/freelance and learning from their mistakes :-)

You can learn some useful wisdom from drug dealers in the show The Wire: always get paid upfront.

Reply on news.ycombinator.com