Re:Using Voice to Code Faster than Keyboard
by itafroma on Tuesday August 13, 2013 @02:07AM
(#6204256)
> A few years into my career the idea of cubicles caught on and quickly became the norm, and now of course we're stuck with these horrible open offices that are, in my experience, just absolutely dreadful for productivity; but since everyone is doing it nobody really notices anymore.
You can largely thank Jim McCarthy of Microsoft fame for that, who in the mid 90s coined the concept, "beware of a guy in a room":
https://www.youtube.com/watch?v=oY6BCHqEbyc
https://blogs.msdn.com/b/david_gristwood/archive/2004/06/24/...
Re:Using Voice to Code Faster than Keyboard
by cocoflunchy on Tuesday August 13, 2013 @12:54AM
(#6204063)
Absolutely relevant article by Joel Spolsky: http://www.joelonsoftware.com/articles/fieldguidetodeveloper...
Re:Using Voice to Code Faster than Keyboard
by shadeless on Tuesday August 13, 2013 @01:27AM
(#6204145)
Also relevant video: https://www.youtube.com/watch?feature=player_detailpage&v=NF...
Re:Using Voice to Code Faster than Keyboard
by JabavuAdams on Tuesday August 13, 2013 @02:27PM
(#6207362)
The fundamental issue is a mismatch between crafting and coordinating roles.
When I'm in a coordination role, open concept is better because I can hear everything in the office and route information accordingly.
When I'm in a crafting role, open concept is death to productivity.
A few years into my career the idea of cubicles caught on and quickly became the norm, and now of course we're stuck with these horrible open offices that are, in my experience, just absolutely dreadful for productivity; but since everyone is doing it nobody really notices anymore.