Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Third Time: a better way to work (2022)

lesswrong.com

Post reply on HN
Print view View original

11–20 of 57 posts

Re: Third Time: a better way to work (2022)

#11

Post by techdmn »

doubled112 wrote: post #9
arturkesik wrote: post #5

Earlier quoted context omitted.

Instead of half-working all day I prefer to work for half a day Parkinson law: "Work expands so as to fill the time available for its completion" Horstman’a corollary: "Work contracts to fit in the time we give it" I used to give myself only 5 hours of work a day in given hours. My productivity was surprisingly better than with full 8 hours, my stress was lower, and I had so much free time. I really should get back t…

I think this has been the biggest benefit to my mental health working from home. The ability to take a minute or thirty when I need it and not wonder what the perception of those around me is. Some of my best ideas come to me as I load the dishwasher. I tend get more done when I can bounce between ideas, projects, states of mind, locations, etc than when I'm powering through something at a desk for hours at a time.

I could never begin to count the times I have been grinding away at something, making zero progress, and the right idea comes to me two minutes after I step away from my machine.

Re: Third Time: a better way to work (2022)

#13

Post by tomjakubowski »

doubled112 wrote: post #9
arturkesik wrote: post #5

Earlier quoted context omitted.

Instead of half-working all day I prefer to work for half a day Parkinson law: "Work expands so as to fill the time available for its completion" Horstman’a corollary: "Work contracts to fit in the time we give it" I used to give myself only 5 hours of work a day in given hours. My productivity was surprisingly better than with full 8 hours, my stress was lower, and I had so much free time. I really should get back t…

I think this has been the biggest benefit to my mental health working from home. The ability to take a minute or thirty when I need it and not wonder what the perception of those around me is. Some of my best ideas come to me as I load the dishwasher. I tend get more done when I can bounce between ideas, projects, states of mind, locations, etc than when I'm powering through something at a desk for hours at a time.

Hammock driven development https://youtube.com/watch?v=f84n5oFoZBc

When I worked in an office I'd get up and go on walks, or move to a sofa and let the problem simmer a bit, several times a day. I've been fortunate to work in companies which seem to, I think, recognize these are productive activities

Re: Third Time: a better way to work (2022)

#15

Post by wdh505 »

foobarian wrote: post #10
zeroonetwothree wrote: post #4

This seems like a huge pain to track if I’m being honest

Well, time's a wastin'! First we'll write a little app, with a sqlite-powered backend maybe throw it behind organizr or something to run at home...

https://rationalbreaks.vercel.app/

Re: Third Time: a better way to work (2022)

#19

Post by TOGoS »

hnthrowaway0328 wrote: post #6

When most of the work is to figure out what the other party wants and what can I take, productivity and motivation practically go down to zero. I need to get into some lower level programming job or a tool programming job.

Same. I wish I got to actually write code. I spend a lot of time at my job knowing that there are programming tasks to be done, but they're not in the sprint, and scrum master will scold me if I work on them, so instead I sit on my hands waiting for the middleware team to do some task or other that would be totally unnecessary if they had followed my advice in the first place.

Re: Third Time: a better way to work (2022)

#20

Post by RIMR »

TOGoS wrote: post #19
hnthrowaway0328 wrote: post #6

When most of the work is to figure out what the other party wants and what can I take, productivity and motivation practically go down to zero. I need to get into some lower level programming job or a tool programming job.

Same. I wish I got to actually write code. I spend a lot of time at my job knowing that there are programming tasks to be done, but they're not in the sprint, and scrum master will scold me if I work on them, so instead I sit on my hands waiting for the middleware team to do some task or other that would be totally unnecessary if they had followed my advice in the first place.

Just work on them anyway, save the code, and follow the ticket. Once it's in the sprint, copy+paste and commit.
Post reply on HN