WelcomeBackSurvey
From MWCSWiki
Here are the aggregate results from the silly survey conducted during the 9/5 "welcome back" party for CPSC students. (31 surveys were returned, though not all questions were answered by all respondents.)
See you at the next party in October!
1. Would you rather...
(a) work for a company that employs 4,000 software developers (25%), or
(b) work for a company that employs 4 software developers? (75%)
2. Would you rather...(a) write a graphics-intensive application in C++ (50%), or
(b) write a Web application in Java? (50%) (an exact tie!)
3. Would you rather...(a) debug somebody's program that uses goto's (19%), or
(b) debug somebody's program that uses global variables? (81%)
4. Would you rather...(a) be a team lead for a project that has two really annoying team members (10%), or
(b) be an ordinary developer on a team with all cool people? (90%)
5. Would you rather...(a) work for a manager who is arrogant (52%), or
(b) work for a manager who is clueless? (48%)
6. Would you rather...(a) write programs in a lab that had lime green walls with gold-colored trim (83%), or
(b) write programs in a lab where “Bette Midler's Greatest Hits” was playing? (17%)
7. Would you rather...(a) write programs in a lab that was 5 degrees too cold (79%), or
(b) write programs in a lab that had a mild, annoying, intermittent buzzing sound? (21%)
8. Would you rather...(a) break out of a loop prematurely, and return at the bottom of the function (50%), or
(b) return from the function right in the middle of the loop? (50%) (another exact tie!)
9. Would you rather...(a) be a designer and developer for a modestly successful company (86%), or
(b) be a tester for an outrageously successful company? (14%)
10. Would you rather...(a) make great contributions to the open source community (57%), or
(b) make big bucks writing expensive, proprietary code? (43%)
11. Would you rather...(a) be guided by design documentation that is about 90% accurate (76%), or
(b) have no documentation at all? (24%)
12. Would you rather...(a) hunt down a bug in somebody else's gnarly code (7%), or
(b) exhaustively document your own beautiful code? (93%)
