4 ms·

>150 hours in a 7 day period Doing what? Just curious. I could only image doing something like that if the job was extremely lax - like a toll booth operator i

by noobly 7y ago

>150 hours in a 7 day period Doing what? Just curious. I could only image doing something like that if the job was extremely lax - like a toll booth operator in a slow town, or something.

AdieuToLogic 7y ago
>> 150 hours in a 7 day period > Doing what? Just curious. I can't speak for the GP (as I am not they), but can say I pulled a 118 hour work week once doing s/w development. Four 20 hour days for one client and the other 38 for another. Suffice to say it was not a fun week.
- oarabbus_ 7y ago
  At that point, wouldn't it have made more sense to set expectations that their 1-week turnaround is realistically a 3-week ask, instead of working 20 hour days?
  - 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 ago
      I 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.
h2odragon 7y ago
IT consulting for nonprofits. "we've spent $50k and the contractor delivered a mockup. Our customer expects us to deliver next week. Build the system." Was to be an integrated Web / IVR phone bot "hotel room reservation" thing built on like the second public release of Asterix; which I'd never heard of before (nor had anyone else). Of course I later found out a cow orker had pocketed the majority of that money and never paid the first contractor for more than the mockup in the first place, something like 3 months ago. They'd bought a domain name and begun planning this more than a year earlier. They'd printed 10,000 high grade outdoor signs which were to be the physical token of subscription to this service. Comes the day and the domain name has expired and been snapped up by someone else. So the launch was delayed by a week so they could print up stickers to put over the signs. In the 3 months the system was up, there were i think 5 attempts to use it. The shafting I got on that one was a big inflection point for me, where it hit me that I wasn't using my time the way I intended, and I wasn't receiving enough reward to justify that. I wish I'd had the thought sooner.

by noobly 7y ago

>150 hours in a 7 day period Doing what? Just curious. I could only image doing something like that if the job was extremely lax - like a toll booth operator in a slow town, or something.

AdieuToLogic 7y ago

>> 150 hours in a 7 day period > Doing what? Just curious. I can't speak for the GP (as I am not they), but can say I pulled a 118 hour work week once doing s/w development. Four 20 hour days for one client and the other 38 for another. Suffice to say it was not a fun week.

oarabbus_ 7y ago
At that point, wouldn't it have made more sense to set expectations that their 1-week turnaround is realistically a 3-week ask, instead of working 20 hour days?
- 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 ago
    I 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.

h2odragon 7y ago

IT consulting for nonprofits. "we've spent $50k and the contractor delivered a mockup. Our customer expects us to deliver next week. Build the system." Was to be an integrated Web / IVR phone bot "hotel room reservation" thing built on like the second public release of Asterix; which I'd never heard of before (nor had anyone else). Of course I later found out a cow orker had pocketed the majority of that money and never paid the first contractor for more than the mockup in the first place, something like 3 months ago. They'd bought a domain name and begun planning this more than a year earlier. They'd printed 10,000 high grade outdoor signs which were to be the physical token of subscription to this service. Comes the day and the domain name has expired and been snapped up by someone else. So the launch was delayed by a week so they could print up stickers to put over the signs. In the 3 months the system was up, there were i think 5 attempts to use it. The shafting I got on that one was a big inflection point for me, where it hit me that I wasn't using my time the way I intended, and I wasn't receiving enough reward to justify that. I wish I'd had the thought sooner.