News for hackers. Stuff that matters.
Re:Down and out in the magic kingdom – A tale of software co... by st3v3r on Friday April 29, 2016 @07:52PM (#11599513)
If you're working for the company, then yes, working until 2am is very much a good reason. Any company that doesn't see this as such is a shit company, plain and simple.
Re:Down and out in the magic kingdom – A tale of software co... by mryan on Saturday April 30, 2016 @04:06AM (#11600865)
> Any company that doesn't see this as such is a shit company, plain and simple.

Nothing is ever that simple. There are perfectly valid reasons for some companies to be unhappy with a contractor unilaterally deciding to work until 2am, and then not turning up for work the next day.

Falling asleep after your manager texts you to see why you haven't turned up for work today is unprofessional, whether you were staying up late night to code or to binge watch Netflix.

Please note that I am talking about this specific situation here. If you are working on your own products or in a team where people view this as expected behaviour, staying up late to take advantage of as many 'in the zone hours' as possible seems like an effective use of a programmer's time.

Re:Down and out in the magic kingdom – A tale of software co... by tptacek on Friday April 29, 2016 @11:21PM (#11600180)
No. Really, really no. Don't work until 2AM for contracting clients. They won't appreciate it; they may the-opposite-of appreciate it.