Lecture 2, Tue 10/06

Setting up team NOTES repo, video on Sohibe Java Code Generator for VSCode

More Programming Assignments coming soon

Dilemma:

• CS changes quickly
• I learn a ton every time I teach the course.
• Dilemma: Do I
  • (a) incorporate everything new that I’ve learned each time I teach the course?
  • (b) accept the fact that I might need to recycle some old, slightly out of date, slightly less than perfect materials?

Right now, I’m trying for (a), which means I still don’t quite have the next assignment ready. Hopefully by Thursday.

The main thing I’m trying to incorporate is:

• Maven from the start.
• Testing as early as possible.

I want to encourage everyone to learn:

• A little bit of vim (Survival vim)
  • Some git commands will through you into vim, and you need to know how to survive
  • When configuring a VM or a new machine, sometimes vim is all you have
• A lot of VSCode
  • VSCode is right in the sweet spot, more than a text editor, but not as heavyweight as most IDES, but most of what you get from IDEs
  • Multiplatform, free
  • Well-maintained, and a great eco-system of extensions

Links for learning basic vim:

• https://ucsb-cs156.github.io/topics/vim/ (the absolute basics)
• https://ucsb-cs156.github.io/topics/vim_basic_eight/ (the most eight more important commands)
• https://ucsb-cs156.github.io/topics/vim_customization/ (line numbers and syntax highlighting)

A little bit on VSCode in today’s video.

Recap of Last Tuesday

Last Tuesday, we gathered in teams, and used the Slack channel to get to know our teammates.

• List of Teams Assignments

We also discussed some of the things that help to make good teams.

On Gauchospace, you should find a participation grade for last Tuesday:

• Ind-10/01 (50 pts) is for your individual participation; you earned this if you make a post with your five items (even if it was after class was over).
• Team-10/01 (50 pts) is for the team portion of your grade; you earned this if you participated in the discussion last Tuesday.

Slack Tip: /whois @name and Time Zone

We have implemented a Slack Bot that allows you to check the GitHub id and team membership of anyone that is part of the class.

Type /whois @slackid in any channel, and you’ll see the person’s name,

Also: if you click on a person’s name on the slack, it will show you the local time in their time zone. This may be important to know if you are collaborating with students in a time zone very different from your own.

An invitation:

• It’s fine to keep your camera off if you need to for:
  • Privacy, Bandwidth, Equipment reasons
• On the other hand:
  • Consider the benefits of turning it on.

Similarly, adding your pronouns (e.g. she/her, he/him, they/them) to your Slack and Zoom handles will help other folks to get those correct. It’s optional but encouraged.

How will grading work in this class?

The syllabus is not yet updated (hope to have that by Thursday), but here’s a breakdown of how your grade will be made up of activities from the following categories:

• Participation Grades (10%) - Each participation grade will be out of 100 points. The grade for 10/01 is an example of this category.

  Particpation grades may vary: some are individual, some are team, and some (like 10/01) may be a combination of the two that adds up to 100.

  The lowest three participation grades will be dropped; accordingly, if you need to miss a lecture every now and then because of illness, internet problems, etc., it shouldn’t affect your grade unless it becomes a persistent problem (in which case you should speak to the instructor as soon as possible about your situation.)

• Homeworks / Quizzes (20 %) - These will sometimes be administered through Gradescope, and sometimes involve making contributions to GitHub repos (as in today’s Homework assignment, H00)

  Some questions will be graded by hand (e.g. short answer/essay type questions), while others might be autograded (e.g. multiple choice, fill in the blank, true/false questions.) These will typically be based on assigned readings. We will drop only the lowest two grades from this category.

• Auto-Graded Programming assignments (30 %) - jpa00 is an example of these programming assignments. None of these will be dropped; you are responsible for all of them. This may include individual assignments (such as jpa00), pair assignments, and/or team assignments.

• Project Grade (40%) - Your project grade will be based on your contributions during the Project phase of the course. We’ll discuss that further on Thursday.

  In addition, we’ll be using peer evaluations through a tool called CATME to assess your individual contributions to the project’s success. The peer evaluation may apply a multiplier to your project grade, increasing it or decreasing it, per your team’s assessment of your contributions. It is important to be sure that you are meeting your committments to your team for a variety of reasons; your grade is among those.

Today’s Team Activity

We’ll be discussing this paper: https://pconrad.github.io/files/paper028.pdf

Our focus will be Section 4, which is divided into 6 sections:

You’ll first assign one person from your team to each section; most teams have six people, so that’s team member per section.

You might use the team slack channel, and use first-come, first-served, or some other way to divide up the sections.

If you have fewer than six team members, you can decide to leave one section uncovered. (If one or more team members is absent, put a slack message in your team channel mentioning them by @-ing them, and letting them know which section(s) are left to be claimed.)

Then, you’ll elect one member of the team as the team scribe (a different one from last time) that can share their screen.

That member of the team should go to the repo for your team on GitHub. Here are links to these repos:

That should currently be an empty, private repo, accessible only to the course staff and the members of your team. The scribe, when they bring up the repo, will see something like the image shown below. Click on the README link to create a README.md file:

Then, your screen will look something like the image below:

• You will see a text area where you can enter text for the README.md file for this repo.
• There are tabs to toggle between Edit and Preview; the format is Markdown, which is explained on This Markdown Cheat Sheet
• You may have to scroll down to find the “Commit New File” button, which is how you save your changes.

What content should you type? Type a list of who is assigned to each section, something like this (you can copy/paste this, then edit it for your group)

# Notes from 10/06

Paper Section Assignments:

* 4.1: Alice Z.
* 4.2: Bob Y.
* 4.3: Chris X.
* 4.4: (unassigned)
* 4.5: Danny W.
* 4.6: Emily V.

Then, save the file. This first part is worth 20% towards your group participation grade; each person assigned to a section earns this if/when this gets committed to GitHub.

Each person now creates a file for their section

Next, each member of the team (individually) should create a file pertaining to their own section. You can do this by following the instructions/images below.

Note: Please follow the naming conventions shown below STRICTLY, including upper vs. lower-case letters.

First, find the “Create New File” button:

Then, start typing the folder name 10.06, as shown. As soon as you type the forward slash /, you should see that the filename turns into a folder name. If you have made a typo, you can hit the delete/backspace key, and it should go back so you can edit the folder name.

Finally, name your file as shown in the example, and fill in content as shown in the example. For now, we only need the heading; the content can come later. The folder name shoudl be 10.061 and the file name should be one of these: sect4.1.md1, sect4.2.md, sect4.3.md1, sect4.4.md, sect4.5.md1, sect4.6.md`.

You earn 50 points towards the individual part of today’s participation when you create your individual part of the repo. You only need the heading; no content yet, that’s for Thursday.

Homework for Thursday

This is your homework for Thursday; you don’t need to do it right now. Just read over it and make sure you understand it.

Between now and Thursday, read over the part of the paper that you were assigned, and think about these questions, and write something in your .md file for each of these questions. This will count as an individual homework grade, H00, due Thursday.

1. (40 pts) For the aspect of software development that you were assigned, the paper describes some aspects of what software development in school is like, vs. what it is like in industry.

   Now consider your own personal experiences in school. Do they line up with what was reported in the paper, or are they different? Is it a mix?

   In your 10.01/sect4.x.md file (where x is one of 1,2,3,4,5 or 6), write briefly about your own personal experiences in school that are relevant to this topic, and how they are the same or different (or a mix of both), as compared to what the interview subjects in the paper reported. Put this under the heading # Question 1.

2. (30 pts) Under the heading # Question 2, answer this question: What are the things that developers found suprising or different about industry in terms of this aspect of software development?

3. (30 pts) Under the heading # Question 3, answer this question: What are suggestions for things students could do in school to better prepare them for this aspect of software development as practiced in industry?

   These can be ideas from the paper, or ideas of your own; either is fine. But in your answer, clearly identify whether each idea is your idea, or one from the paper.

What happens after Thursday with this paper

After Thursday, we’ll ask each of you to read the answers of your teammates. Then, next week, be prepared for a full discussion of the paper. There will be more questions to answer then.

Checklist

1. Double check that someone on the team has set the README.md of your team’s team-xpm-y-NOTES repo to have the correct content (list of who is assigned to which section, with a heading of # Notes from 10/06

2. Double check that each member of the team that’s present has create a file in that repo under a folder called 10.06 with the correct content (a file that’s one of (sect4.1.md1, sect4.2.md, etc.) and that the content of that file matches the instructions above. It only needs to be a header at this point.

What then?

Three options:

• Watch a 20 minute video about VS Code and the Sohibe Code Generators (now or sometime between now and Thursday)
• Ask for help with jpa00
• AMA with course staff

The video on VS Code

Then, I have some lecture material. Because it seems silly to have you sit for lecture material “synchronously”, I will try my best to make videos when we have lecture material. However, those take much longer to produce that you might think, even if you don’t do a super fastidious job of editing.

Here’s the first video: my hope is that the SD version will be ready just in time for lecture. The HD version might be ready a little later.

• https://youtu.be/mGrP-kfYHew