Lecture 00 Next Lecture

Lecture 00, Tue 03/29

Introduction to CS156

https://ucsb-cs156.github.io/s22/lectures/lect00

Please sit with your team:

Seating Chart

Announcement from one of your classmates:

image

My special passion: Teaching real world software practice

Why is this course different from all other courses?

Because as a young software developer I saw a gap between what I learned in school, and what i needed in industry.

What’s this course about?

Helping prepare you for transition from “Computer Science Student” to “Professional Software Dev”

What’s different?

Dimension CS Student Professional SW Dev
What: Differences in Scope well-defined, fixed scope vague, open-ended, evolving scope
When: Short vs. Long Time Spans short time spans (days, weeks) long time spans (months, years)
Who: Individual vs. Large Team individuals, pairs, small groups larger teams
Why: Learning vs. User Needs to learn something to address a user need
How: Ad-Hoc vs. Professional ad-hoc tools and practices professional tools and formal practices
How Big: Small vs. Large Codebases small programs large complex systems

How the course runs

Format: Not so much lecture

The course website

Here: https://ucsb-cs156.github.io

Note the two parts:

Also note the Calendar where you can keep track of things that are due: https://ucsb-cs156.github.io/s22/info/calendar/

Where is the syllabus?

Here:

A few items from syllabus

Grade breakdown:

image

How the project grade works:

Getting Started With Java Programming

The first programming assignment is here: https://ucsb-cs156.github.io/s22/lab/jpa00/

The second programming assignment, jpa01 is a bit more challenging, since it deals with something called “mutation testing” that may be new to you. I’ll cover some of that in lecture on Wednesday.

It is available now as well and on Gradescope. It is due at the end of next week, but I encourage you to start it sooner.

If you haven’t joined the GitHub organization yet, DO IT NOW.

Literally, right now, during class.

If you get the message that your “email didn’t match anyone on the course roster”, then:

The first two programming assignments, plus our in-class work for Tuesday, depend on having everyone in the GitHub org, so please do that now.

Homework

For tomorrow (Wednesday discussion)

Reading in the Textbook (reading for H00 due Friday).

This homework assignment due Friday is based on:

Homework H00 due Friday

https://ucsb-cs156.github.io/s22/hwk/h00

What will we learn in this class:

Two halves:

Legacy Applications: They existed before this course started, and will continue to exist in the future.

Logistics

Where can you find info in this class?

Now we meet our first team

We’ll now separate into teams, (and/or go into breakout rooms if online) and you’ll meet the first team you’ll be working with during the course.

Teams are by discussion section; there are three discussion sections, and 4 teams per discussion section.

Team assignments, and the mapping from teams to staff (LAs/TAs) is listed here:

Note that while the instructor, or a TA or LA might drop in on your Breakout Room, they are not the discussion leader. You need to self-organize to run your own breakout room discussion.

What to do in your breakout room

This part is 40% of your participation grade for today (P00 on Gauchospace)

  1. Please choose someone to be the discussion leader, and someone else to be the scribe. Note that you’ll be asked to rotate these roles each time we have a session, so that everyone gets a chance to practice their leadership skills and their writing skills.

    You could also choose to rotate the scribe during the session; that’s up to you. Stick with one discussion leader for today though, to make things less confusing. (of course if your discussion leader loses their internet connection half way through class, you’ll have to improvise.)

  2. Everyone log in to the Slack in another window (Zoom open in one window, slack in another.)

    Everyone find the Slack channel for your team. It will have a name such as s22-5pm-3. Everyone on the team join that channel, and introduce yourself with a post.

    The post should include

    • (a) The name you like to be called
    • (b) Your pronouns (e.g. she/her/hers, he/him/his, they/them/theirs)
    • (c) Your computing platform(s): Windows, Mac, Linux, or WSL (Windows Subsystem for Linux)
    • (d) Optional: Something interesting about yourself (this may be unrelated to Computing)
    • (e) Optional: Something you are hoping to learn in this course

    Completing this step earn you 60% of the participation points for today’s class, and you earn those as an individual. (This part can be made up later.)

    The remaining 40% comes as a “group grade” when your group completes the questions below (note that you must be present in class to earn this part.)

  3. The person who is the scribe should:
    • Find the Slack channel for the team
    • “share their screen”, so that everyone else can see what they are typing.

    The scribe should record who the discussion leader is for the group, and whether you are sticking with one scribe, or rotating for each question. Just make a post in your group’s slack channel with this information.

  4. The discussion leader should give everyone time to find the slack channel, and make their first post.

    Then, ask the following questions of the group. The scribe can record the group’s answers.

    Each of these is worth 10% towards your group’s particpation grade for today’s activity. The discussion leader should note that there are five questions, so be sure to allocate the time appropriately, and move on to the next question as needed.

    • Question 1: Every team is a group of people, but not every group of people functions as a team.

      Think about when you’ve been part of a successful team. As a group, identify at least three things that are true of a team that functions well. You could probably identify many more, but for today, stop at three so you have time for the remaining questions.

    • Question 2: There are a variety of dimensions of “success” for a team.

      One dimension is the “outcome” of what they produce, e.g. do they win the game, or make the product, etc.

      Another dimension is the “process” by which they accomplish that. That dimension includes aspects such as:

      • the way in which the team members work together either in harmony, or in conflict,
      • whether there is an equitable sharing of the workload or one that feels inequitable
      • whether team members feel safe and respected, or unsafe and disrespected

      Identify three things that your team in this course might do to ensure good process, without sacrificing the quality of the “outcome”. (These might or might not overlap with your answers to question 1; it’s ok if they do, but try to think about it from a different perspective. Question 1 is more about memories of past successful teams, while this question is more about looking forward to what you’ll do with this team and any other temas are you are part of in CMPSC 156.)

    • Question 3: On a team, there are often people with different levels of prior experience and knowledge for the given task. Your team likely has different levels of prior experience, knowledge, and current skill level with in a variety of areas, such as Java, JavaScript, git, GitHub, databases, HTML, CSS, and Agile just to name a few topics.

      Those varying levels of experience can be a stumbling block, but they don’t have to be.

      Think of three challenges that might arise because of differnet levels of experience.

    • Question 4: Now, for each of the challenges you listed above, come up with a strategy that a team could use to address that challenge, and put the team on the path to success.

If time remains, here’s what to do with it

If you complete these four questions, with the time remaining, you are invited to discuss with one another your prior experience with these technologies, and record some of that discussion in your Slack channel.

It’s totally fine if you have no experience with any of these things. Success in this course is defined by learning, which is the change between where you start and where you end up at the end of the course. So, don’t worry about comparing yourself to others and feeling like you don’t belong.

We ask because the staff can construct a better learning experience for everyone if we know where people are starting.

Which of these areas are ones where you have some prior experience, and which are areas where you are a complete beginner?

What are you most interested to learn in this course?

Record as much of your conversation as you are able in the Slack channel