Skip to content

Latest commit

 

History

History
95 lines (62 loc) · 3.81 KB

HW0-Pipelines.md

File metadata and controls

95 lines (62 loc) · 3.81 KB

HW0

This homework will prepare you for basic setup for the course.

Basic course setup (20)

Slack+Moodle (10)

Properly setting up your Slack and Moodle profile by providing a picture will help the teaching staff learn your name. Upload a current headshot picture of you (not anyone else, not a cartoon picture of you, etc.) to your Moodle profile. For Slack, make sure you have your first and last name as part of your profile. Use US passport photo guidelines.

Github (10)

Sign into NCSU's GitHub.

  1. Create a private repo called HW0.
  2. Go to Settings, Collaborators and Teams, and add the TAs and instructor as a collaborator (using their unity id).

Shrikant Shete [email protected], Sam Mirhosseini Ghamsa [email protected], Christopher Parnin [email protected]

Computing Environment (20)

Create virtual machine image using vagrant and virtual box. Install node.js. Demonstrate using a sync folder.

Pipeline (40)

Complete the pipelines workshop.

Screencast (20)

Create a screencast demoing your computing environment and pipeline.

Submit

Submit a link to your github repo to here containing the following:

  • Complete moodle and slack profiles by deadline (20).
  • Computing Environment (20)
  • Pipeline (40)
  • Screencast (20)

Create a README.md that describes your submission and includes screenshots. Include a link to your screencast video.

Due Thursday, 1/18, before midnight.

Screencasts/Demo Gifs Guidelines

Here are some guidelines and links for creating good screencasts. It is good to get ready now to learn how to create demo videos for your future project milestones and career.

A general guideline: Do whatever it would do if you were teaching someone how to do something. For example, you don’t have to show people you typing and creating the whole commit, but you might want to show the contents of the hook in a text editor, before doing a commit.

Software
Guidelines for both multimedia formats:
  • Keep the content simple - A regular software engineer without knowing anything about your tool should be able to follow you
Guidelines for screencasts (video)
  • Mention your name, unity ID and the tool/source code which you will be testing/demoing when you begin
  • Use a headset microphone for good quality audio recording.
  • Create a script and rehearse that script
Guidelines for making a screencast:
More advice

http://assets.techsmith.com/Docs/pdf-camtasiaStudio/Create_Engaging_Screencasts.pdf