Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I mean, sure. But if you have a typical programming job, it's not like there's a clean finish line. There's always more work to do, but at some point you need to pack up and go home for the night.


then your employer needs to plan better and descope where required


No, dude. Like, not, "There's always omigod super important crunch time work to do." There's always just ordinary "what's next on the queue" work to do. Descoping doesn't mean "We're done as software developers," it means "We aren't going to worry about getting this functionality into this release."

But there's no point where you don't have a backlog. When you finish the task you're current working on, you pick up the next task. Nobody's expecting anyone to work all night on the next task, but similarly there's no place where you're like, "Okay, we're done, everyone go home for the week." So... work 40 hours-ish.


Sounds like your employer sucks mate and probably a weak or ineffectual CTO who is not doing their job




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: