CS462 FAQ

The following are some frequently asked questions about CS462:

  1. I've never used Linux before. Will I be able to pass this course? 

    Yes, plenty of people who've never used Linux before have successfully completed this course in the past. You'll catch on quick. I'd recommend that you don't form groups with others who have no Linux experience, unless it can't be helped. Its always nice when someone can mentor the others.

  2. I've heard that this class is a lot of work. Is that true? 

    Yes. Tell your {spouse,{girl,boy}friend} that you'll miss them, but you'll return at the end of the semester better for the experience. I'm warning you right now that this class can be more work than what you might expect a 3 credit class to have. If you're not prepared for the workload, bail out now rather than whining later.

  3. I've not had CS340, but I'm taking it now, is that OK? 

    Yes. Concurrent enrollment is OK. Read the information about prerequisites. 

  4. I've not had CS360. Is that OK? 

    Not unless you have other experience which includes much of the same material. I assume that you understand the basics taught in CS360. It's not fair to other students for me to go back an explain these concepts again. We'll review the ones we need for the class, but just that...review. Read the information about prerequisites. 

  5. I don't want to use Ubuntu, I'm used to Fedora (Debian, Suse, Mandrake, etc.). Can I use another Linux? 

    Yes, you're welcome to use any OS you like. However, class examples will necessarily be on a specific OS. The TA and professor may not know the details of the OS you choose. 

  6. I'd rather use PERL/PHP/Java/C#/Cobol/FORTH. Can I? 

    You're free to use any language you like unless specifically required by the assignment.

  7. I worked really hard in the class and I only got a C+, I don't understand. 

    In this class, as in other aspects of life, you are graded on results, not effort.

    • Good intentions aren't good enough.
    • Good decisions aren't good enough.
    • Good analysis isn't good enough.
    • Good planning isn't good enough.
    • Good systems and processes aren't good enough.
    • Good implementation isn't good enough.
    • Even good ethics aren't good enough.

    All of these will likely be necessary, but the results are what count. I can't judge your effort or intentions, I can only judge what you turn in. Your boss will not give you a raise and your clients and customers will not continue to buy from you just because you tried really hard. That lesson is more important than anything else I could teach you.