See also, this assignment on Canvas: https://ucsb.instructure.com/courses/21167/assignments/262224

Today’s Team Activity

This activity works with the paper that you were told about on the first day of class:

You do not need to have read the whole thing for today, but having at least skimmed it will help inform your choice of section to be responsible for.

  • The title of this paper is Listening to Early Career Developers
  • I’ll call this paper LTD for short (i.e. Listening To Developers)

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

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

You’ll first assign one person from your team to each section; most teams have six people, so that’s one 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 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.

(While I don’t think this applies today, because all teams currently have six members, but if someone does drop before this activity is completed, as as a result, you have fewer than six team members, you can decide to leave one section uncovered.)

Then, please choose one member of the team as the team scribe (preferably, 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:

Team NOTES repo Slack
f24-01 f24-01-NOTES Slack
f24-02 f24-02-NOTES Slack
f24-03 f24-03-NOTES Slack
f24-04 f24-04-NOTES Slack
f24-05 f24-05-NOTES Slack
f24-06 f24-06-NOTES Slack
f24-07 f24-07-NOTES Slack
f24-08 f24-08-NOTES Slack
f24-09 f24-09-NOTES Slack
f24-10 f24-10-NOTES Slack
f24-11 f24-11-NOTES Slack
f24-12 f24-12-NOTES Slack
f24-13 f24-13-NOTES Slack
f24-14 f24-14-NOTES Slack
f24-15 f24-15-NOTES Slack
f24-16 f24-16-NOTES Slack

Each of those 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:

click-to-create-README

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.

new-README-50

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)

The heading should look like this: # Notes from 

# Notes from (date)

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.

If you have fewer than six team members, one or more sections may end up unassigned.

But if you have members that are part of your team but merely absent from class, them team should assign them to a section, and notify them via the team slack channel of the section they were assigned to.

When you’ve added this content, save the file and commit it 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:

Create-new-file-50

Then, start typing the folder name , 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. Please use p05 as the folder name:

image

image

Finally, name your file as shown in the example below, and fill in content as shown in the example.

image

The folder name should be and the file name should be one of these: sect4.1.md, sect4.2.md, sect4.3.md, sect4.4.md, sect4.5.md, sect4.6.md.

You earn today’s participation when you create your individual part of the repo. You only need the heading for today; the rest of the content is part of H01.

What happens after today’s class?

For lecture this coming Tuesday, please be prepared for a full discussion of the paper. You also have a homework assignnent, that will be due next Tuesday. There will be more questions to answer then.

Checklist for today’s work

  1. Double check that someone on the team has set the README.md of your team’s f24-xx-NOTES repo to have the correct content (list of who is assigned to which section, with a heading of

    # Notes from

  2. Double check that each member of the team that’s present has create a file in that repo under a folder called p05 with the correct content (a file that’s one of (sect4.1.md, 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.

  3. Then, submit a link to your repo to p05

What then?

If there’s any time left in class after you’ve finished, here are some suggestions for how to use that time:

  • If there is any part of the Install Checklist that you haven’t finished, now is a good time to get help with that.
  • If that’s all done, you can: