4 ms·

Let me tell you something about labs. Challenging labs a) are REALLY hard to make and b) ALWAYS suck on the first iteration, ALWAYS. This guy has set back the

Let me tell you something about labs. Challenging labs a) are REALLY hard to make and b) ALWAYS suck on the first iteration, ALWAYS. This guy has set back the whole course to the very beginning, because now everything needs to be rewritten. He's a jerk. No one's impressed by his sophomore-level introductory data structures and algo classes. And because he posted his code to the public, I have the following comments: his code is poorly commented and kind of crappy. I'm further bothered by the fact that he's a senior-to-be and hasn't done anything substantial yet. Where's the kernel, 1337 freedom of information defender?

jrockway 17y ago
This guy has set back the whole course to the very beginning, because now everything needs to be rewritten. So? As someone who is not a student there, I could also read the labs and post my take on the code. Information wants to be free. Anyway, my advice would have been to take down the code when asked. Wait a week (until grades are published), then put the code back up. By that time, everyone will have forgotten. (People are very, very lazy.) I'm further bothered by the fact that he's a senior-to-be and hasn't done anything substantial yet. Where's the kernel, 1337 freedom of information defender? I don't think undergrads ever do anything substantial (as part of their official coursework, that is). So I would not fault this guy for that, that is a problem with the system in general.
- alexgartrell 17y ago
  Professors can fail students at any point between starting the class and graduation. Piss one off bad enough and he'll change your grade. True on the lazy part though. At the risk of being that guy, at _my_ school, many undergrad CS majors write an honest-to-god ground up Kernel. So, from scratch to able to boot on x86 hardware and run multiple different programs and everything. Arguably substantial.
- philwelch 17y ago
  "I don't think undergrads ever do anything substantial (as part of their official coursework, that is)." Really? I've heard of: -Systems programming: Implement ext2. -Operating systems: Write a kernel. -Compilers: Write a compiler for a C-like language. and that's at my school alone. Though 2 of those are senior level classes, systems is a junior level class. I just assumed that's how CS was done everywhere. Want to learn about (foo)s? Write a foo!

jrockway 17y ago

This guy has set back the whole course to the very beginning, because now everything needs to be rewritten. So? As someone who is not a student there, I could also read the labs and post my take on the code. Information wants to be free. Anyway, my advice would have been to take down the code when asked. Wait a week (until grades are published), then put the code back up. By that time, everyone will have forgotten. (People are very, very lazy.) I'm further bothered by the fact that he's a senior-to-be and hasn't done anything substantial yet. Where's the kernel, 1337 freedom of information defender? I don't think undergrads ever do anything substantial (as part of their official coursework, that is). So I would not fault this guy for that, that is a problem with the system in general.

alexgartrell 17y ago
Professors can fail students at any point between starting the class and graduation. Piss one off bad enough and he'll change your grade. True on the lazy part though. At the risk of being that guy, at _my_ school, many undergrad CS majors write an honest-to-god ground up Kernel. So, from scratch to able to boot on x86 hardware and run multiple different programs and everything. Arguably substantial.
philwelch 17y ago
"I don't think undergrads ever do anything substantial (as part of their official coursework, that is)." Really? I've heard of: -Systems programming: Implement ext2. -Operating systems: Write a kernel. -Compilers: Write a compiler for a C-like language. and that's at my school alone. Though 2 of those are senior level classes, systems is a junior level class. I just assumed that's how CS was done everywhere. Want to learn about (foo)s? Write a foo!