Live data from Hacker News

Ask HN: How do you decide when you've done enough work for the day?

news.ycombinator.com

111–120 of 123 posts

Re: Ask HN: How do you decide when you've done enough work for the day?

#111
post #41

Earlier quoted context omitted.

Amen. Working on my own products has never caused any kind of fatigue. It’s energizing :)

I find there is inevitably still tough days working for yourself on a project that takes more than a month. Overworking can lead to losing sight of your goals which can lead to burn out.

Fair enough! Breaks and structure remain important.

I wake up every morning at 5:00, do some excersises, write down my goals, do pushups until I can’t any more and then process all emails from the past 24 hours. Once that’s done I set a todo list for that day and push things forward that aren’t a priority.

So far, this ensures I’m able to stay on top, don’t lose track, can work 10 to 12 hours a day easily and not feel tired or unproductive.

There’s still plenty of time left for “life” as well. Just have to be in bed at 22:30 at the very latest.

Setting goals, cooking every day and adhering to that routine works wonders to be honest, I highly recommend it :)

Re: Ask HN: How do you decide when you've done enough work for the day?

#112
post #38

Earlier quoted context omitted.

Amazing how I wrote this post without typing anything in it, I bill by estimate so if something is estimated 40 hours and I do it in 2, I can get more work or just chill, I usually book my time around 200 "hours" a week and some good weeks I work 18 real hours and the bad ones around 70, pays extremely well but has very little margin for error so the bad weeks have to be rare. I had 18 straight months of good weeks a…

How do you handle deployments on those "40" hour projects? I understand that you provide that much value, but it the client thinks they are paying for hours, even if not directly, seeing a contractor push code in 2 hours and then bill me for 40 has to hurt a bit. Obviously if your estimate is devoid of any hourly numbers, this conversation is moot.

Those are closed price projects, they do use hours for reports and all but its really a fixed payout for a fixed amount of features.

Re: Ask HN: How do you decide when you've done enough work for the day?

#113
Humans work in cycles.

So, you already had the right hunch.

You don't really have a good direction on a random day and can't really get into the zone? Fix some small bugs for 2h and then call it quits, go to the gym, drink beer with your friends.

You got that one feature that you know exactly how you build it and you're on fire for it? Knock yourself out in a coding session of 2 x 20h and take 3 days off afterwards. Much bette than forcing yourself to quit at 6pm even though you're burning to do it.

Productivity means taking advantage of the human cycle, which is comprised of your mood, hormones, the characteristic of your problem and many more factors that you can't really control.

Re: Ask HN: How do you decide when you've done enough work for the day?

#114
post #74

I know this is not bery popular point of view on HN but: Burn out? You are in your mid 20ies, if you can’t put in long hours and hard work now you won’t be able to do it later in life trust me. It really comes down to how industrious and conscientious you are rather then how smart and happy you are. If you’re a hard worker and know your job well you will make it on any job, even the ones with shitty management. If th…

> It really comes down to how industrious and conscientious you are rather then how smart and happy you are.

I get it that industriousness and conscientiousness are important, but I disagree that "it" (whatever "it" is) comes down to those rather than being happy.

(I also disagree that being smart or working smart is less important, although it's true that just being smart without any of the former two doesn't allow one to accomplish much. Of course if you value the idea of being busy and doing a lot as an end in itself, that's another story.)

If your economical circumstances, the surrounding society or other realities dictate that you have to be particularly industrious in order to survive and to meet your basic needs, wants and goals, it makes sense to have that as your central value. But if you're already getting what you need, why on Earth would industriousness rule over happiness or satisfaction?

I guess this is pretty much a matter of values, and if you get that satisfaction from being and feeling industrious, that kind of answers the question. But if you don't, it doesn't make much sense -- in that case the former is just a means to the end.

> Most people don’t have this luxury, work very long hours in completely shitty jobs (think cleaning toilets) and never burn out and lead happy life.

Well, you can kind of toil away in a non-thinking job, and if it suits your personality, that's fine. It can still be exhausting particularly if you need to do it in a hurry, but I wouldn't expect you to burn out if you can keep doing pretty much the same thing every day and it suits you.

However, I think a lot of people on HN are the kinds of people who get satisfaction from more than just getting their basic job done, and the ability to be creative and to maintain the kinds of cognitive abilities required e.g. for tech jobs does actually require a balance, at least for most people.

But yeah, it's a matter of values in a sense I guess. Doing what fits your values gives satisfaction.

Re: Ask HN: How do you decide when you've done enough work for the day?

#116
I spend the first 70% of the work day on hard problems and things I absolutely have to get done. For me this 70% ends at 4pm.

At 4, I step out for a coffee, stroll around the block and grab a cookie. Then I come back to my table and reply to annoying emails and tackle the easy stuff till about 6-6:30.

I never start working on a tough problem after lunch, because if things go wrong, I end up working long hours and can't get it out of my head even when I go back home.

By the way, I'm really impressed that many people commenting here can work 6-10 hours at a stretch. I need to stretch every 45 minutes to 1 hour lol.

Re: Ask HN: How do you decide when you've done enough work for the day?

#117
post #64

This is what works for me. 1. Start the day with a plan (15 to 30 min) 2. List things that, absolutely, need to be completed 3. List things that would be great if can be completed (bonus) 4. Have a set time when you are going to finish work. For me, 6pm. So when 3 or 4pm hits and I still have 1 or 2 things from my list #2 above, I get on it right away. That also helps me to stay on track whenever I am in meeting or u…

Making lists on sticky notes, and crumpling them up when they're done, is the best feeling and reaaaally makes you feel accomplished. :-)

Re: Ask HN: How do you decide when you've done enough work for the day?

#118
In this past job which was the first one that didn't track time at all, I still wrote down my hours every day and still tried to balance it to +/- 0 at the end of the week, if not possible then end of the month. After a while (months?) I did what everyone else seemed to do. Just eyeball if it's either roughly 40 hours per week or if the last days/week was very stressful tread a little more careful, or if nothing seemed to work and I was distracted make a mental note to catch up next week.

That said, I enjoyed most of my time there very much and often would be doing exploratory stuff that I might have done on my own time anyway, so sometimes I took some extra time to evaluate one more possibility and used some spare time. Other times I just did some private stuff only veeery distantly related to actual work stuff and chalked it up as "learning".

So yeah, probably not a really helpful answer. But if you're having fun and are learning a lot a few more hours won't hurt. If a fun evening of spare time does not include programming (which I guess is true for at least 50% of programmers) then don't put in extra time. I think I've mostly done "I have a guilty conscience if I leave a lot sooner" but I also try really hard to not slack off during my 8 hours and count them as working hours. And yes, if you have that "Today I achieved more in 6 hours than the whole last week" then absolutely stop working, it's probably true.

Re: Ask HN: How do you decide when you've done enough work for the day?

#119
Pedantic guy asks "what is your definition of 'work'"?

The short answer for me is, I've done enough 'work' when my efficiency curve drops more than 15-20%.

After that though I relax my scanning the latest news, HN and other consistent sources of interesting and useful new information. Is this work? Actually I (as in the guy in my brain who uses it when I'm not) often comes up with work arounds for the local maximum I've often hit in my "real work". Things like a better way to structure some code, a better way to approach a system problem, all kinds of useful things pop up from time to time. Really it's a way of getting out of the rut.

I've come to view this as essential work though it seems like just goofing off.

Well the Brits have a saying for it. "Bed, bath and bus." That's often where inspiration strikes when you least expected.

Re: Ask HN: How do you decide when you've done enough work for the day?

#120
post #32
post #7

How strict is your employer about butt-in-seat schedule? If you have full flexibility, I’d suggest aiming to hit 40 hours on a weekly basis rather than 8 on a daily basis. That gives you the flexibility to work, say, 10 hours one day because you’re really on a roll, and to stop at 6 hours the next afternoon when you’re tired and distracted without feeling guilty. Don’t go over 40 hours on a regular basis. That’s a re…

From my own experience, burnout is primarily emotional . Time spent is a side-effect. It's not how many hours you work, it's how much of your experience involves despair, frustration, and resentment. That might either be towards your employer ("stupid schedules, I'm not valued"), towards yourself ("this should be easy but I'm failing"), or towards the universe for simply not being the way it "should" be.

Beautifully put.
Post reply on HN