Weekly Journal

An important way for you to improve is by practicing mindful learning, pausing and reflecting during an activity, so that the context of your actions is not lost. An important way for us to understand what you have learned is make your learning visible and, unfortunately, code alone is not enough. Thus, to help even programmers like you improve and to help us understand how you are learning, you will practice regular journaling throughout the semester.

Informal writing can clarify your thinking and improve your ability to remember, observe, think, and communicate. When you are writing your journal entries, do not be overly concerned about grammar. It is more important for these weekly entries to communicate ideas effectively, focus on ideas, depth, and critical analysis — tackle concepts rather than worry about splitting infinitives. The object of the journal is not to simply regurgitate the readings or lecture content (or let ChatGPT generate thoughts on your behalf) but to develop your own connections between the theoretical (or philosophical) and practical elements of the course and a better understanding of your relationship to coding.

Just write — you might even find it fun!

Submitting Your Work

Journals are due each week by 3:08am ET in the morning on the day after that given on the course Calendar (effectively a few extra hours grace time past midnight).

• You will be graded only on what you push on the main branch of the individual portfolio_NETID repository provided for you in the course's Gitlab group
• You are responsible for ensuring that all files are in the repository on time (so make sure you backup regularly (i.e.., by using GIT!))
• Each entry must be in a separate file in the journals folder, named for the number of the week and topic (e.g., week01_autobiography.md)
  Templates to start each entry are given below that are named correctly using this convention.
• You must use the Markdown format for your entries, whose specific prompts are detailed below

Markdown is an industry standard, simple, plain text format for providing style guidelines that can be transformed into any other document format. IntelliJ includes a Markdown editor that provides a preview or there are web-based editors that provides similar functionality.

Deliverables

1. CompSci Autobiography (template)
2. Thinking about Ethics and Failure (template)
3. Breakout Project Analysis (template)
4. Starting and Learning Reflection (template)
5. Cell Society Teamwork Reflection (template)
6. Cell Society Project Analysis (template)
7. Ethics in the News (template)
8. Testing and Reflection (template)
9. Spring Break
10. SLogo Teamwork Reflection (template)
11. SLogo Project Analysis (template)
12. Professional Ethics (template)
13. Personal Ethics (template)
14. OOGASalad Project Midpoint Reflection (template)
15. Improvement Assessment (template)
16. OOGASalad Teamwork Reflection (template)
17. OOGASalad Project Analysis (template)