←back to thread

282 points _vaporwave_ | 1 comments | | HN request time: 0s | source
Show context
Waterluvian ◴[] No.44999915[source]
Some days an interruption will throw me off my train of thought, and I spend the remaining six hours collecting discarded bottles and railway ties for hopeful use somewhere, somehow, sometime.

Other days an interruption costs me pretty much nothing.

I’m still trying to figure out how to tell which of those days I’m going to have and whether to just not log into Slack for the day.

replies(14): >>44999940 #>>45000121 #>>45000236 #>>45000314 #>>45000493 #>>45001283 #>>45001447 #>>45001905 #>>45001941 #>>45002030 #>>45002057 #>>45003807 #>>45005151 #>>45005448 #
karmakaze ◴[] No.45000493[source]
I've found one thing that minimizes interruption cost: pair programming. At one startup we pair programmed all day, every day. Resuming from an interruption was almost seamless. Can't explain it, only experienced it.
replies(8): >>45000671 #>>45000685 #>>45000970 #>>45001512 #>>45002084 #>>45002294 #>>45007473 #>>45007708 #
1. steve1977 ◴[] No.45001512[source]
I guess pair programming would also minimize my interruption cost, but only because productivity would be close to zero to begin with.