Aktuelle Änderungen Printable View Änderungen Bearbeiten
TailRecursionElimination > Recursion > TddScratch > TeamFoundationServer > TeamFoundationVersionControl > Technorati > TedNelson > TemplateDriven > TestDriven > TestDrivenDevelopment > TestDrivenDesign > TestDrivenDevelopment > TheArtOfComputerProgramming > TheBug > TheFitChallenge > TheFlow > FlowClear Trail
a state where work flows
being "in the zone"
Flow takes time to achieve, and it is fragile. If a programmer's flow is interrupted it can take a large amount of time for her to regain the state, sometimes up to an hour. That's an hour of lost productivity to your team. If a programmer is interrupted many times during the day she may never reach this state. Without this state, creativity is crippled.
Flow is fragile but, thankfully, it isn't as fragile as it first seems. Flow can only be broken if an interruption requires a programmer to mentally change contexts.
I’ve been working for years at getting better about interruptions. I love the flow state, but I think that we programmers make it too fragile when we try to keep everything in our head. The thing is that always seems like you are almost there, so the time to write down anything about your stacked task is a waste of time. I’ve been fighting that tendency, with varying degrees of success.
My solution, as you mentioned, is to resist the temptation to do the latest thing in my head right away and to write it down somewhere so that my mind can relax and know that it’s accounted for somewhere.
that’s the key right there. The ability to mentally “relax”, sure that you won’t lose track, leads to a prolongation and enhancement of the flow state.