How to destroy Programmer Productivity
georgestocker.com
How to destroy Programmer Productivity
1–10 of 30 posts
Re: How to destroy Programmer Productivity
#2I work in an office but I felt the productivity graph is still pretty accurate for me as well. WFH does wonders for me as it avoids most of the randomization I get from coworkers.
Re: How to destroy Programmer Productivity
#3The "red dots" are fantastic. One of the reasons I've always preferred to work at night is that my achievements for a given work period are judged all at once as a lump sum the next morning vs how hard I "appear to be working" when observed at random intervals during a day shift.
Re: How to destroy Programmer Productivity
#4I have been a developer for a little more than a month now and what I have discovered is that although the office is open, whenever someone passes you, they treat you like you are in some kind of a no-distraction bubble, even if you get along really well. I have become to respect that culture.
Re: How to destroy Programmer Productivity
#5I have been a developer for a little more than a month now and what I have discovered is that although the office is open, whenever someone passes you, they treat you like you are in some kind of a no-distraction bubble, even if you get along really well. I have become to respect that culture.
It's the exact opposite at my work place...
Re: How to destroy Programmer Productivity
#6I seem to be having less trouble with bouts of unproductiveness ever since I started sleeping 9 hours (at least) almost every night. This practice was discussed just the other day here on HN [0]. I've been doing it for a year or so.
I'm not saying that my periods of reduced productivity are completely gone, but they seem to be shorter and less severe.
Re: How to destroy Programmer Productivity
#7Programmer productivity is also very hard to measure. Just this afternoon I finally nailed a tough problem that I 'd banged my head against for weeks and then set aside while I was watching an episode of The Glades, when I should have been "working". Goofing off can be highly productive.
Re: How to destroy Programmer Productivity
#8Programmer productivity is also very hard to measure. Just this afternoon I finally nailed a tough problem that I 'd banged my head against for weeks and then set aside while I was watching an episode of The Glades, when I should have been "working". Goofing off can be highly productive.
When I hit a wall - shower or gym.
Re: How to destroy Programmer Productivity
#9Programmer productivity is also very hard to measure. Just this afternoon I finally nailed a tough problem that I 'd banged my head against for weeks and then set aside while I was watching an episode of The Glades, when I should have been "working". Goofing off can be highly productive.
sure it is hard to measure objectively, but I can tell I am significantly less productive than 3 years ago when I started my job. There were just two of us in the office, so either we were talking with each other or concentrating. Now there are 4 and constant interruptions.
I suppose it is because the in house database I have been building and maintaining is used more heavily and as such I am a source of knowledge for a lot of stuff that goes on in the organisation as a result. I am personally less productive, but the organisation is more productive. Now if only I could persuade the users to read the error messages and think for a minute ("there is no sample in the database with the name blah" ), rather than come straight to me and ask me to fix it, then we would all be a lot more efficient.
Re: How to destroy Programmer Productivity
#10That is so true! Also i discovered i'm way more productive in winter, than in this summer period. Just last few days ago i was thinking how to make me more productive, so now i decided to change a little bit my workspace, it should bring back my productivness i guess.