←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 #
SoftTalker ◴[] No.45000671[source]
If only I wouldn’t prefer stabbing myself in the leg with a rusty knife over pair programming.
replies(9): >>45000690 #>>45000909 #>>45000936 #>>45000950 #>>45001156 #>>45001994 #>>45002151 #>>45003045 #>>45004772 #
dylan604 ◴[] No.45000690[source]
I've never done official pair programming, but I get frustrated when I'm not on the keyboard as I find others think slower.
replies(6): >>45000835 #>>45000842 #>>45001070 #>>45001123 #>>45004510 #>>45004715 #
1. karmakaze ◴[] No.45001070{4}[source]
I usually prefer to be navigator than driver. It's the navigator that does the high level thinking. The one at the keyboard is the one who's usually better at typing and writing out the design patterns that are agreed upon. Of course we did swap roles routinely, maybe several times a day. Oh and to top it off we switched pairing partners every week or two. It was a brutal experiment but I learned a lot and I'd say it was a great success.