Week 01 Tutorial Questions

  1. Introduce yourselves, get to know your classmates - Why do they want to study computing? What do they want to learn from this course?
  2. Get to know your tutor - How long have they been at UNSW? What are they studying? How can you get in contact with them?
  3. Do you have any questions about the course so far? eg course website, structure, assessments
  4. Is it OK to ask a really really basic question on the course forum?
  5. I have a brain the size of a planet and been writing C programs since pre-school - do I need to read the course forum?
  6. How do you make a peanut-butter sandwich?

    How could you break that process into steps?

    How could you break it down clearly enough that a computer could understand it?

    Maybe your tutor could do a live demonstration of following your exact instructions...

  7. What is an operating system?

    What operating systems do your classmates run? The tute room? The CSE lab computers?

    What are the differences between each of the various operating systems? What differences are there in their interfaces, and how do you interact with them?

    What are some different ways in which you can interact with a computer?

    What are the differences between graphical user interfaces and the command line? When might one be better than the other?

  8. In an ideal world we'd have the first COMP1511 lecture of the week before the first tutorial of the week.

    As we only have 10 weeks of teaching, we don't want to lose one just because it's before the first lecture.

    This means if you have a tut-lab on Monday, you haven't had the lecture the following questions talk about.

    Even without the first lecture, Tutorials and Labs are still worth having because you get to meet and know your tutor, your fellow students and see the lab environment.

    For tutorials before the first lecture - tutors will try to explain what they can as part of the tutorial but don't worry if you don't understand lots of things.

    Of course there are no marks for the week 1 tut-lab.

    If you have a chance to watch it, here's a video of last year's first lecture:

    A video of the 2019 term 3 COMP1511 lecture But if you can't watch the video don't worry.
    Discuss the following features of the sample program from lectures:

    // Basic Hello World program
    // Marc Chee, June 2019
    
    #include <stdio.h>
    
    int main (void) {
        printf("Hello World\n");
        return 0;
    }
    
    • the \n
    • Comments: What should go in a comment? What makes a good comment? How do comments improve program style?
    • Indenting and whitespace: What is indented in the sample program? Suggest why.
  9. Write a C program, face0.c, that behaves as follows:
    ./face0
    ~ ~
    0 0
     o
     -
    
    
    How would you compile this program?
    How could we modify it to make a program, face1.c, look like this instead?
    ./face1
    ~ ~
    0 0
     o
    \_/
    
    
  10. Logging In - This is the first part of the Lab, but since you can't see it in the lab until after you log in, the information is here:

    Once you are in your lab, one student from your pair should log into the lab computer.

    To log in, you use your zID (which looks something like z1234567) and your zPass (which is used to log into all other university online services).

    The CSE labs use the Linux operating system (not Windows or OSX or ...).

    When you log in, by default, you'll be using the xfce4 window manager, and you'll see a linux desktop.

    If you are asked to select a panel click on use default settings.

    Along with menus that you can see, such as the Applications Menu in the top left corner, it also has a simple menu you can access by right-clicking anywhere on the desktop.

    Have a look around and see if you can work out how to open a web browser.