My take on the 50h thing for a project deadline after my previous employer: screw it. If you are going to do a 50h week for some period of time, you are not going to have a successful project. The end result of that is more 50h weeks to fix it.
user55340
Thus, screw it, acknowledge that you're going to blow the deadline, and reset expectations and scope that maintains the sanity of the people developing the software.
user41796
@MichaelT I think it depends. And I want to say Brooks' claims would back that. Overtime can work when it's capped in duration (1 week, maybe 1 month) and those participating are given down time to recover from the extra work.
user55340
If you don't maintain their sanity, they will get new jobs - especially if conditions that brought about the 50h weeks in the first place are not rectified. Losing 75% of your development team (happened at my last job) does not make for good support of the project going forward.
user41796
But there's definitely a curve for total amount of OT in the week and the results you get. And it's definitely not a linear increase in the productivity either.
user55340
Thus, my take on the "am I letting my team down by not also doing 50h" is "no, you're letting the team down by not pushing for a reset of expectations and you may find yourself with much less of a team afterwards. Especially if its clear that the next project will also have mandatory 50s at the end of it too."
@GlenH7 Nope. Not done. I just had a meeting (long one). Still don't understand: WTH is in the IP header then? The UDP header has destination, port, size, all the shit necessary for the routing et al. So what's in the IP header that's not duplicated in the UDP header?
user41796
@MichaelT I definitely agree with that. OT like that has to be an exception with no chance of it becoming the rule.
The Whiteboard
The Whiteboard