From personal experience (I'm a software engineer that works pretty long hours), I've found that it's more important to pick things with the hope of avoiding annoyance, rather than anticipating what I think would be nice in the future.
Things I've discovered:
1) You can't have too much desktop space.
I somehow scored an apple 30" cinema display for my desk at work-- and it's a godsend. I could care less about the coolness factor of it-- it's the resolution that helps me. If you're going to be running multiple terminals, debuggers, etc., then consider 1600x1200 and a 21" monitor a MINIMUM setup-- 1920x1440 on a 24" monitor is MUCH better, and obviously 2560x1600 on a 30" is amazing. You'll laugh when coworkers are hunting around their screens, minimizing window after window, to find something that is obfuscated. This one is often overlooked, but trust me... the added cost of a larger monitor is COMPLETELY worth it!
2) If you have unpadded arm rests, or your arms sit on your desk as your type, your elbows WILL hurt eventually.
Get an office chair with padded arm rests that isn't too soft in the seat or backrest areas-- also, lumbar support is helpful when sitting for a long time.
3) If you're doing development on a large project that is in a compiled language, get a dual CPU box, or use distcc (in the case of C/C++) with multiple machines.
You'll be amazed at how much faster "make -j4" is on a dual-CPU opteron than "make" is on a single-cpu opteron when recompiling your latest code change. This is an often overlooked workstation feature!
4) Get a machine with a fast hard drive
Just like #3 above-- compiling C/C++ projects sucks when you have a slow machine... get a machine with a fast hard drive. Ultra320 SCSI drives are excellent for this sort of thing, but I believe a high-end SATA drive would do well too.
Bottom line is-- you should use whatever editor, GUI tool, debugger, etc. that you know the best, and are most comfortable with. Your setup should allow you to use those same tools more efficiently and comfortably.
Building 1 might be ass-kicking high tech... but I think building 2 recieved significantly less funding. When i was moving from building 2 to Calvert Hall (where I'm at now), my golf clubs were stolen from the building's lobby. Response from management? Don't worry... We have a security camera in there!... (1 week later)... Sorry, the security camera wasn't on.
Wherever you are-- thanks, asshole. I hope you suck at golf.
I'm currently a CS student at the University of Maryland.
I know several people who have been accused of cheating after the "cheat software" detected code similarities... Were they guilty? Yep.
A member of the honor council came to one of our lectures to discuss the problem of cheating in CS... She said that the majority of cases that their board sees are from the CS department. Is that because there is more cheating in CS? I don't think so -- I think it's because CS takes greater care to detect and appropriately punish cheating than other departments.
One of our CS professors talked about the "cheat detection" program that they use, and described it as very accurate (i.e. when it flags two sets of code as being similar, they usually are to the point of great suspicion)
I really have no objection to the use of a system like this -- our CS projects are always large enough such that -great- similarities between students' work shouldn't exist.
Slashdot Mirror
From personal experience (I'm a software engineer that works pretty long hours), I've found that it's more important to pick things with the hope of avoiding annoyance, rather than anticipating what I think would be nice in the future.
Things I've discovered:
1) You can't have too much desktop space.
I somehow scored an apple 30" cinema display for my desk at work-- and it's a godsend. I could care less about the coolness factor of it-- it's the resolution that helps me. If you're going to be running multiple terminals, debuggers, etc., then consider 1600x1200 and a 21" monitor a MINIMUM setup-- 1920x1440 on a 24" monitor is MUCH better, and obviously 2560x1600 on a 30" is amazing. You'll laugh when coworkers are hunting around their screens, minimizing window after window, to find something that is obfuscated. This one is often overlooked, but trust me... the added cost of a larger monitor is COMPLETELY worth it!
2) If you have unpadded arm rests, or your arms sit on your desk as your type, your elbows WILL hurt eventually.
Get an office chair with padded arm rests that isn't too soft in the seat or backrest areas-- also, lumbar support is helpful when sitting for a long time.
3) If you're doing development on a large project that is in a compiled language, get a dual CPU box, or use distcc (in the case of C/C++) with multiple machines.
You'll be amazed at how much faster "make -j4" is on a dual-CPU opteron than "make" is on a single-cpu opteron when recompiling your latest code change. This is an often overlooked workstation feature!
4) Get a machine with a fast hard drive
Just like #3 above-- compiling C/C++ projects sucks when you have a slow machine... get a machine with a fast hard drive. Ultra320 SCSI drives are excellent for this sort of thing, but I believe a high-end SATA drive would do well too.
Bottom line is-- you should use whatever editor, GUI tool, debugger, etc. that you know the best, and are most comfortable with. Your setup should allow you to use those same tools more efficiently and comfortably.
In that video clip, I swear I saw Mark McKinney as Darrill, the artsy loser, from the kids in the hall. Maybe it's just the ponytail.
I lived in commons building 2 over the summer (sublet)... Pretty nice place...
n d/
... (1 week later) ... Sorry, the security camera wasn't on.
http://www.capstonecompanies.com/locations/maryla
Building 1 might be ass-kicking high tech... but I think building 2 recieved significantly less funding. When i was moving from building 2 to Calvert Hall (where I'm at now), my golf clubs were stolen from the building's lobby. Response from management? Don't worry... We have a security camera in there!
Wherever you are-- thanks, asshole. I hope you suck at golf.
Somebody please mod the above reply up. I laughed so hard i almost recycled popcorn.
How can one breast be "Redundant"?
I'm currently a CS student at the University of Maryland.
I know several people who have been accused of cheating after the "cheat software" detected code similarities... Were they guilty? Yep.
A member of the honor council came to one of our lectures to discuss the problem of cheating in CS... She said that the majority of cases that their board sees are from the CS department. Is that because there is more cheating in CS? I don't think so -- I think it's because CS takes greater care to detect and appropriately punish cheating than other departments.
One of our CS professors talked about the "cheat detection" program that they use, and described it as very accurate (i.e. when it flags two sets of code as being similar, they usually are to the point of great suspicion)
I really have no objection to the use of a system like this -- our CS projects are always large enough such that -great- similarities between students' work shouldn't exist.
P = {you're one of those people that actually got an A in discrete math}
Q = {I hate you}
P -> Q
It's a shame that other sites don't accomodate those of us that speak sweedish chef.
That's why google is on top.
(This post -barely- passed the lameness filter)
Ass.
I sure hope the gamecube turns out more like my american-made laptop and automobile that are both falling apart.
Nintendo Site: http://www.nintendo.com/systems/gcn/gcn_overview.j sp
= Disassembled+Gamecube&inc=gcopen.inc
Disassembled GameCube: http://www.lik-sang.com/catalog/master.php?navbar
Info on GameCube Console from GameCube Central: http://tomoeslab.virtualave.net/consoleinfo.html