Hacker News new | ask | show | jobs
by r00fus 2440 days ago
As someone who works with client billable hours, actual work usually takes the least amount of time. The communication about your completion, testing/confirmation, documentation and shadow/knowledge sharing take the remaining 7.5h (using your analogy).

If you're truly doing all those things in 30m, you should be running the show.

Sometimes taking the full 8h allows you to put in the packaging to confirm you've done the "hard" part.

1 comments

Everyone in this thread below is assuming after the 30 minutes I just fuck off and do nothing. LOL, why would anyone pay me if I did that? Obviously, there's always a ton of stuff to do. But, again, it's about results, not hours worked. There's times when you have to put in almost 48 hours non-stop, others where you don't have to work all week. The point is that if your employees have tasks to do and they're doing them, who gives a fuck about how long it takes them? The 40 hour work week is fucking horrible, anyway, and as is pointed out later in this thread, creative work like coding goes on in your mind pretty much 24/7. If I come up with the solution to a problem Saturday night you can damn well be sure I'm taking some time off to compensate for that. Otherwise I'll burn the fuck out.

Sure, some unknown quantity of people can just fuck around and hide from work, but again, you're not paying me because I'm a fuck off person, yer paying me because I have the decades of experience, and because you know with certainty I'll do the damn work, find more work when I need more, and will never miss a deadline on my own fault. Everyone on HN just assumes bad faith all the time, geez....