DSGN 270 - Dated Journal Entries
Four journal entries will be submitted for DSGN 270 in 2 rounds.
- Example from Jan 17, 2022 lesson
- Tony's code journal
Round 1: January 17-19
- Submission 1
Round 2: March 9-14
- Submissions 2,
Requirements
- Entries are dated within the date range of the course or within the due date of an assignment.
- Git commits should be dated no more than a day after the date listed in the entry. This is to ensure entries are authentic.
- The content of the entry focuses on one or more learning objectives of DSGN 270.
Marking Rubric
Each entry will be worth 5 points, for a total of 10 points. 2.5 points will be given for the following:
1. Self-assessment
Learning objective: To accurately self-assess learning performance.
Full marks
- Student has demonstrated accurate self-assessment skills and/or has demonstrated quantifiable improvement toward their learning goals.
Partial marks
- There are areas for improvement. For example:
- Learning goal(s) is not concrete/precise;
- Performance metrics are not quantifiable;
- More reflection needed.
Minimal marks
- Little or no attempt was made to self-assess learning performance.
2. Proof of Work
Learning objective: To capture learning artifacts (code, references, ideas, reminders, etc) for future review by the student, classmates or instructor.
Full marks
- At least three artifacts have been recorded in the entry.
Half marks
- Less than three artifacts have been recorded in the entry.
Minimal marks
- Little or no proof of work has been recorded.
Submission Instructions
- Accepted locations for dated entries:
- As an entry in your dedicated
code-journal
repo; - In the README of a relevant remote repo (project, assignment, etc) under the heading "Code Journal".
- As an entry in your dedicated
- Zip your dated entry and submit it to Brightspace.
- As a comment to your submission, include:
- a link to the specific file and heading of your dated entry.
- Example: Jan 1st entry in Tony's
code-journal
- Example: Jan 1st entry in Tony's
- a link to the specific file and heading of your dated entry.
Example content
Self-assessment
- What concrete and precise goals have you set for yourself?
- "I want to set aside a half-hour every day, dedicated to coding"
- "I want to get a great search result with phrase that's 3 words or less"
- "I want to push a commit every day"
- "I want to review the Prep before every class"
- "I want to attempt one tutorial every Lab Time this week"
- What metrics are you basing your performance on?
- the search terms you're using
- GitHub activity
- number of labs completed in class
- amount of time spent coding
- number of pair-coding sessions attempted
- Are you meeting the expectations you've set for yourself?
- What steps can you take to learn more effectively?
- What are today's wins?
Proof of Work
- Lab/tutorial/exercise attempts
- What concrete and precise goal do you have for the session? What problem are you trying to solve?
- What's the plan?
- Numbered steps you've taken to complete the objective
- Observations, obstacles encountered, solutions found.
- Links to starting and finishing commits (if applicable)
- Reflection: was the objective achieved? Why or why not?
- Class notes
- video timestamp markers for important information
- instructor/classmate quotes
- observations
- helpful/useful links pasted in the Chat
- questions for later
- reminders for Lab Time
- What topics covered in class has interested you the most?
- TODOs
- Research sessions
- What questions do you want to answer?
- What search terms are you using?
- Could the author/content creator be a good source for information in the future?
- Useful links, resources and attributions