Colorado State University Logo | Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3) Colorado State University Logo | Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)
Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)
Computer Science

Virtual Help Desk Instructions

The TAs will be posting hours in which they will be available on the Microsoft Team for the class.

In general, we ask that you contact us (both TAs, and the instructor) on Microsoft Teams (don’t use email / canvas - unless it is a long message), this can be via direct message or general channel for open questions.

We also will be running a virtual help desk over Microsoft teams. As the MS teams is not designed to be a help desk queue, we have developed the following procedure for asking for help.

  1. In general chat, you should ask general questions (do NOT post your code)
    • You should do this first, as talking through a problem often helps you solve it!
    • Good questions to ask are “I am looking at problem X, and I think the algorithm is as follows… (English line by line). What are your thoughts?”
    • A bad question is “I am stuck on problem X.”, as it leaves people to guess what is going on instead of helping directly.
    • This allows anyone in the class to help answer your question, not just TAs, building both the community and larger response time.
    • While we say don’t post your code, posting algorithms is fine, or provided code from lecture / labs. It is also fine to post links to help sites, as long as this is not abused.
  2. Coding questions
    1. Post in general chat (during TA hours): “I have a coding question on (lab x:step y, practical x, etc)”
    2. TAs will be going through them in order, putting a :thumbs up: emote on questions they are helping with
    3. They will then direct message you, asking for your question
      • note: response times can vary, but if you are not around when they respond, they will have to move on.
    4. You will then respond with your question + code.
      • For a better response, just don’t say send code. Instead, send a question with what you have tried, along with the code. Try explaining your code in your message.
      • Remember your formatting options, especially the format code option </>
        MS Teams Format Banner
      • Also, if you just paste the code into Teams from your IDE, it automatically formats the code - so pretty easy to make code look nice.
      • This means there is no reason to send screenshots of your code! Please don’t, they are hard to work with.
      • Depending on your question, your TA may ask you to go into teams videochat, and screen share with them. Please make sure this is setup correctly.
    5. After your question is answered, your TA will put a smiley face next to the “I have a coding question…” message in general chat. Please note, the answer to your question could be to try a few things, and then come back. They may still put a smiley face for tracking purposes, and if they direct you to message them directly after that, it is fine.
    6. After your question is answered, we ask that you wait a bit before posting “I have a coding question”, and if you immediately continue to do that - they may move you to the bottom of the ‘queue’ in order to help other students.
  3. During non-standard lab times, feel free to send a direct message. TAs will answer during their office hours. TAs are tagged with the TA tag.

As a last reminder, the more you can have a general question, as compared to a coding question - the more you will learn! We encourage general questions to all students to see and discuss.

Additional Debugging Advice

When coding, there is a lot of debugging. We suggest the following to help / try before asking coding questions. Please note that if you have general / insight question, these don’t apply. However, trying these debugging techniques before asking coding questions will help you become a better programmer.

  • Design before you code
    • the best developers build a plan before coding. They figure out what they want to do, either by writing it in comments or using paper. It makes a major difference.
  • Talk through your code / algorithm (see ducky below)
  • Write code in small segments (one or two lines at a time)
    • make sure it compiles
    • toss in a System.out.println() to make sure it is doing what you think
    • this may mean adding extra variables
  • Have a bug, use printlns liberally to figure out what is going on
    • this may mean commenting out sections of your code, and slowly stepping through it
    • we suggest using “TESTING” or “DEBUG” in whatever you print. That way, you don’t accidentally leave a print in there when you submit for grading.

Before asking questions, talk to the ducky!

Often the best thing you can do is explain what you are attempting to do to a friend. In the process of explaining it, you usually figure out your errors, and it helps give you a direction to go from there.

Sometimes in companies, this can be a time-cost for other developers so thus the introduction of a Rubber Duck for testing. This gives you an object for you to talk to just like you would a friend. The object doesn’t have to give feedback (just like a friend doesn’t), but instead, the process of talking through the code out loud will often provide insights into both development and errors.

Computer Science Department

279 Computer Science Building
1100 Centre Avenue
Fort Collins, CO 80523
Phone: (970) 491-5792
Fax: (970) 491-2466

Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)

Survey of computer science, formal logic, and computational thinking. Explores the historical, gender, and cultural perspectives on the role of technology in society. Includes learning a basic programming language. Students will be expected to write small programs, and construct written arguments on ways in which technology influences our modern culture. Previous computer science experience not necessary.