How to become a dramatically better programmer

Re:How to become a dramatically better programmer by eksapsy on Monday June 11, 2018 @11:40PM (#17290545)

There was one point where I just disagreed from my standpoint. The pomodoro technique.

In programming for me, it never really worked. I mean, let's say I just got an idea for a specific piece of code, if the pomodoro triggers a break, I just lost my line of thought. When I'll get back after the 5 minute break, I will no longer remember what I was doing or how exactly I thought doing it.

I don't really know if for you folks it worked, but for me for this reason it didn't work and it never probably will.

[ Parent | on HN ]

Re:How to become a dramatically better programmer by rossdavidh on Tuesday June 12, 2018 @11:31AM (#17294229)

I can believe it works differently for others, but for me the pomodoro technique works very well. When I'm "in the zone" and banging away, I am much more likely to _fail_ to notice that there is a much easier approach that I could be trying. Interrupting my work occasionally for a few minutes, and then coming back, vastly increases the odds I will realize, "oh wait, instead of spending the next three hours doing this thing here, I could change a bit of this other part of the codebase and not even need that."

Just my experience.

[ Parent | on HN ]