CIS 163 Introduction

• CIS 163 is tough. For everybody
  • For most students, this is the first time you can’t effectively just code “off the top of your head”
    • “blueprint” analogy
    • Need to save time in your schedule for work to expand into.
  • Bottom line: You need to be able to program fluently.
    • When you can speak fluently, you are able to focus on the content of your message (i.e., what you want to say) instead of the delivery (i.e. how to say it)
    • That means you need to be able to program well enough that you can focus on the algorithm rather than syntax.
  • 163 will be especially tough if you got less than a B 162
  • Almost impossible for students who got Cs.
    • Especially in a 12-week class
  • Again, regardless of the actual grade, you need to be fluent.
• Academic Honesty
  • Became a big problem last semester
  • Handing suspected cheating takes a lot of time and effort.
  • Also degrades the perceived quality of the program.
    • I.e., harms the students who have already graduated.
  • We need to take a zero-tolerance approach.
    • We can no longer afford to offer the benefit of the doubt.
  • Bottom line: Do not look at completed code unless your own code is done.
    • Don’t ask to see a friend’s solution
    • Don’t google for completed solutions online
    • Don’t hire help at UpWork, Chegg, etc.
  • When in doubt, seek help through official channels
    • Instructors
    • CIS success center
    • Tutors

  • You are encouraged to help each other. Just don’t do it by sharing code.

  • Plan for the course
    • Meet synchronously online
    • Use BB Collaborate session for lecture / lab
    • Use BB Collaborate “Course Room” for office hours.
    • I plan to record and post most lectures.
    • Some lectures will be prepared and posted in advance.
    • Since we aren’t relying on a physical lab, lab times may move a bit (i.e., not always be W 6 to 8.)
      • For example, we’ll use some of this week’s “lab” time tonight to help everybody get set up.
    • I will be as flexible as possible; but, given the difficulty level of the course, I hesitate to make it asynchronous. I don’t want to be giving out a bunch of Ds and Fs in August.
• I can put links to lecture right on the course home page.
  • That makes it easy to access them; but,
  • Anybody browsing the Internet can watch them.
• Alternately, I can make them accessible only through BlackBoard; but, then it’s not as easy to get to them.
• I don’t anticipate discussing any private/sensitive material in class
• Poll: Any objections to keeping lectures “open”?

• Please remind me to begin recording every lecture.

• Poll
  • I can only meet during the scheduled MW time
  • I prefer to meet during the MW time
  • Let’s find a different time to meet
• Office Hours:
  • Officially MW 9 to 10.
  • But, just email to arrange another time. I can easily jump on BB almost any time.

• Course Management:

• Course web page: https://www.cis.gvsu.edu/~kurmasz/Teaching/Courses/S20/CIS163
  • This is your starting point when looking for information
  • Syllabus
  • List of Assignments
  • Timeline. (Look here for “what did I miss” or “when is it due” type questions)
• Blackboard: Used only for
  • Grades
  • BB Collaborate
• Piazza
  • Announcements
  • General questions (e.g., questions about class or homework)
  • If the question might apply to more than one person, please post it to Piazza rather than email.
• Discord:
  • A place for you to post less-serious stuff / let out some frustration
  • I don’t typically monitor Discord; but, when asked, I’m happy to jump on and chat.
• Email
  • Private / personal questions (e.g., questions about grades)
  • Request office hours appointment.

Ready to get started?

• Get set up with Git.
• Open project in Visual Studio code.