3 ms·
That's a difficult argument to make when you're contracting or a consultant and are expected to deliver X and not work Z hour.
by LilBytes 7y ago
That's a difficult argument to make when you're contracting or a consultant and are expected to deliver X and not work Z hour.
- oarabbus_ 7y agoI know, and I've been there. There, meaning working absurd extra hours in order to deliver to the client as reneging would mean I have to own up to the client the fact that I totally fucked up the scoping (usually it's scope creep or changing requirements, but you can't really blame them even if it's their fault). I've done that before, and perhaps other people here are getting paid more to consult than I, but it's not worth it IMO to sacrifice your life for the client.
- AdieuToLogic 7y ago> There, meaning working absurd extra hours in order to deliver to the client as reneging would mean I have to own up to the client the fact that I totally fucked up the scoping (usually it's scope creep or changing requirements, but you can't really blame them even if it's their fault). The client for which I did the four 20 hour days had a project manager that committed to a milestone delivery with their client and did not run it past the dev team. So I did everything possible in order to deliver for the client. Were it that I underestimated the scope of work (which I have done many times), I definitely would have conveyed that.