= 27d567bc2d48d9f40e9ccc20ea370b15)
luminosity comments on Anti-akrasia remote monitoring experiment - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (114)
This is like pair programming except you don't have to cut your productivity nearly in half.
To clarify: I've always believed that most of the benefit from the practice comes from the fact that work is actually being done for an increased portion of the time in front of the monitor, and that the costs and benefits of discussion roughly balance.
Anecdotal, but my experience of pair programming is that it's incredibly useful for picking up bugs as they are laid down rather than having to dig them up later. Not to say that being monitored working doesn't help, but finding and removing bugs is by far the hardest and most expensive part of programming.
Seems reasonable and is supported by some study linked in Wikipedia. Code review is supposed to do this more efficiently, albeit with higher latency.