View on GitHub

COMP 491/492

Dickinson College Computer Science Senior Seminar

WA01 - Drafting a Reflective Blog Post

An important part of learning about and understanding issues is to reflect upon them after reading and discussion. This gives you a chance to process the information, organize your thoughts, incorporate insights from others. To gain practice with this, you will be writing reflective blog posts related to our class discussions on technical and social/legal/ethical issues in computing. You are given wide latitude in these posts to reflect/expand on some aspect of one of the reading/discussion topics that was of interest to you.

You will be completing one blog post in the fall semester and several in the spring semester. In the fall semester we will break the process of writing and revising the post into three separate assignments. In this assignment (WA01), you will write a full, polished draft of your post. In the second assignment (WA02), you will be giving feedback to your peers on their posts and receiving receive feedback from them on yours. Ultimately in the third assignment (WA03), you will revise your post based on that feedback and post it on a public-facing blog.

Assignment

The following links to later sections of this document provide the details of this assignment:

  1. Select a topic about which to write.
  2. Familiarize yourself with the expected style of writing that is expected.
  3. Write your blog post.
  4. Submit the Assignment.

Additional Details

Selecting a Topic

You are given wide latitude to choose a topic for your blog post and you are encouraged to use it as an opportunity to learn more about something that is of interest to you. However, the topic you select must:

Expected Writing Style

The expected writing style for your blog post is exemplified by the blog posts in the Science + Tech section of The Conversation. You should familiarize yourself with the expected style of writing by reading a few of these posts and then try to emulate their style in your writing.

Blog Posts on Blog Posts

You can also go meta and read some blog posts about writing blog posts. Here are a few that are pretty good:

If those don’t work for you there is no shortage of other advice, just google “How to write a blog post” or “How to write a technical blog post” and find something that resonates with you and matches the goals of this assignment.

Using AI for Revision

Recall that the AI Use policy in the course Syllabus allows you to use AI to revise writing you have already completed as long as you retain a copy of your original work. The following sites have some useful suggestions on how to use AI for revision that are compatible with the course policy:

Writing the Blog Post

Well written blog posts that receive high scores will:

In addition, you should consider explicitly licensing your content using a Creative Commons License so that others know how they may and may not use your work.

Submitting the Assignment

Submit your assignment as follows:

  1. Ensure that your Dickinson WiD Repository on GitHub is well organized.
    • There should be one folder for each course (e.g. COMP132, COMP256, etc…)
    • All content should be stored in the folder for the appropriate course.
  2. Create a COMP491 folder in your Dickinson WiD Repository.
  3. If you used an AI to help with editing and revision of your blog post, you must upload a PDF of the original (pre-AI revision) version to your Dickinson WiD Repository. Name this file using a filename that ends with -preAIHelp.pdf.
  4. Ensure that your draft blog post does not contain your name. This is important for the peer review process in (WA02).
  5. Create a PDF of your draft blog post with a filename that ends with -draft.pdf.
  6. Place the PDF that you created in your new COMP491 folder.

Acknowledgements

This assignment builds from and adapts ideas and content from the following activities created by others:


Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License All textual materials used in this course are licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

GPL V3 or Later All executable code used in this course is licensed under the GNU General Public License Version 3 or later