= 27d567bc2d48d9f40e9ccc20ea370b15)
Vaniver comments on Open Thread, May 18 - May 24, 2015 - Less Wrong Discussion
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 (176)
If using multiple screens at work made you more productive, care to give an example or two what do you put on one and the other and how they interact? Perhaps also negatives, in what situations that doesn't help?
Hypothesis: they only work with transformation type work e.g. translation where you read a document in one and translate in another, or read a spec in one and write code to implement it in another or at any rate the output you generate is strongly dependent on an input that you need to keep referring to.
I actually borrowed a TV as a second screen because I need to re-create the layouts of document reports from an old accounting software in a new. So it is handy to have the example on the TV while I work on the new one. Of course a printout on a music-stand would work just as well...
I of course do much of the "work on A, reference on B" that others have talked about--the IDE open on one screen and the documentation open on the other--but it's also worth pointing out the cases where there are multiple pieces of reference material that I'm trying to collide somehow, and having both of them open simultaneously is obviously incredible useful.