Overview

• Students will keep a record (a "journal" or "blog") of activities in the the CS2613 labs.

• This journal will be worth 12% of your course mark in total.

• The journal will be maintained using frog and git. See the first lab for a tutorial.

• The marking rubric available

Content

• Each journal entry should be a minumum of 500 words and a (rough) maximum of 1000

• You can think about your journal entry as a set of notes for a friend who missed this particular lab.

• Your journal entry should answer the following questions

  • What new concepts (if any) did you learn about in this lab?
  • What concepts are familiar from other courses or from your own knowledge?
  • What new skills did you practice?
  • What specific details did you find surprising, interesting, confusing, difficult, or otherwise important?
  • What explicit tasks (e.g. reading) were you given during this lab?

• You are encouraged to link to other pages both inside and outside UNB in your journal entries.

Presentation

• Imagine a future employer reading your journal right before interviewing you. Write so that the person interviewing will think of you as a peer, rather than as an "annoying kid".

• Your journal entry should use good spelling and grammar, including complete sentences and paragraphs.

• A certain amount of point form is OK, but don't rely on it exclusively.

• Try to keep a neutral tone. It's fine to record positive or negative opinions, but avoid ranting (or gushing).

• Avoid overuse of emoticons or slang.

Handing it it

• Your journal must be handed in via pushing to coursegit

• I recommend you commit and push some rough notes during the lab and edit them later.

• You can commit and push as many times as you like. You will be marked on what is on the server at the time it is due.

• By default your journal is only visible to the prof and the TA.

Deliverables

• Create a separate post for each lab.

• This journal entry must be in the standard directory, and must be named <date>-<title>.md or <date>-<title>.scrbl where <date> is the date of the corresponding lab. Any easy way to ensure this is to create the journal entry during the lab.

• Make sure you preview your journal entry to avoid obvious mistakes. You will lose marks for syntax errors.

CS2613 Journal batch 1
Thu 16 Jan 2025 04:30:00 PM

CS2613 Journal batch 2
Thu 30 Jan 2025 04:30:00 PM

CS2613 journal batch 3
Thu 03 Apr 2025 04:30:00 PM