COURSE REFLECTIONS
Reflection on Technical Definitions Assignment
Writing the first draft of the Technical Definition
For the technical definition assignment, we were asked to simplify a complex term for non-technical audiences. This was achieved through writing three different definitions: a parenthetical definition, a sentence definition, and an expanded definition. This task challenged my understanding of the term algorithm. The concept of algorithms is second-nature to me, but this assignment clarified blind spots in my understanding. For instance, I struggled with the construction of the sentence definition. In doing so, I realized I did not truly understand where algorithms fit in the larger scope of the field of computer science. In a similar fashion, the expanded definition broke down the bare bones of algorithmic processing (sequence, selection and iteration blocks). This supplemented the depth of my own understanding. This assignment also served as practice for writing to different audiences, and as a formal introduction to parenthetical, sentence and expanded definitions.
Peer Review Process
During the peer review process, I was tasked to read and review my team member’s (Christine Hsiao) draft of the definition of deductible. Through reading my team member’s work, I was able to see possible revisions needed in my own work. For example, Christine’s draft was more concisely constructed, and every sentence served its own point. This inspired me to cut down on some unnecessary elaboration in my own assignment. Reading another student’s work also clarified the possible ways one can approach this assignment. My approach was more heavily focused on the raw definition of the term algorithm, but my teammate emphasized her term in relation to PharmaCare patients. This illuminated my understanding of the realm of possibilities this assignment could take. Overall, the peer review process was a critical step for my final draft.
Final Revision
After receiving feedback, I was tasked with revising the assignment. Since I agreed with all of the feedback my teammate gave me, I revised accordingly. For example, my teammate pointed out that my draft tended to use the passive voice rather than the active voice. I would have never noticed this oversight without her feedback. As well, revising the draft after a few days allowed me to see it with fresh eyes. I cut down on unnecessarily wordy sentences, and simplified the “analysis of parts” segment. Further, the instructor’s guidance helped in eliminating pronouns for the polished draft. Wholly, the final revision process helped me produce work that was to the best of my ability.
Reflection on Unit 2 Assignments
Reflection on LinkedIn Best Practices
It was eye-opening to research effective LinkedIn profiles. As someone who has a mostly inactive profile, this assignment revealed clear instructions on how to make the best use of my professional network. For example, Schaffer’s emphasis on being an active user illuminated a weakness in my current LinkedIn practices. As well, suggestions like following school alumni and using relevant hashtags gave me direct steps I could take to improve my approach. In the summer of 2022, I hope to find an internship or co-op in the tech industry. This assignment gave me tips on how to clean up my LinkedIn profile for prospective employers.
Reflection on Report Proposal
Forming a report proposal was a very interesting and new process. While I have done research papers in the past, they typically focused on the use of scholarly articles and journals. This was my first experience in investigating a real-world issue through direct community interaction. I found the process of creating and reviewing the survey for going paperless in CPSC 121 insightful. Notably, it was difficult to strike a balance on prying on the issue without being critical, but I think I managed to be sufficiently neutral. I hope to interview Dr. Mochetti about student feedback and concerns in the near future, and consolidate her perspective into the final report. I am a bit concerned on how to effectively tie together student and professor stances to propose a final solution (ie. students seem to largely prefer paper-based midterms). Regardless, the process of creating a formal report proposal highlighted the nuances and intricacies of going paperless in classes that have discrete math components.
Reflection on the Peer Review Process
The peer review process has made me more aware of the existing weaknesses in my work. For example, my partner Christine Hsiao noticed that certain areas of my proposal were unclear, such as the problem statement. She also emphasized conciseness for the proposal solution. In some ways, I find that when I am doing my first draft, there are certain areas that I am unsure about. These are often the same areas that are later confirmed by my peer review partner. On the flip side, the experience of peer reviewing my partner’s work highlighted the contentious nature of certain issues within the community. For instance, my partner’s proposal aimed to increase inclusivity in the UBC International Navigator Club. One of the proposed solutions was to limit native language speak, and to punish those who infringed on the rule. My peer review affirmed the need for sensitivity when dealing with these kinds of concerns. That is to say, through this process, I have learned that peer reviewing truly goes beyond just grammar, spelling and following course guidelines, and can delve into ethical implications. In this way, the peer review process provides an invaluable second opinion.
Reflection on Web Folio
Reflection on the Creation of the Web Folio
It was fulfilling to tie together the course material and my past work to create a web folio for ENG 301. The process made me reflect on what makes an effective web folio. For instance, I tried to incorporate as many pictures and visuals as possible for easy readability. As well, although this web folio is specifically dedicated to ENG 301, it provided me with inspiration on how to go about developing my own cohesive portfolio when searching for a software-development related position.
I also found the process of editing and correcting my work to be a very important step. Since a significant amount of time has passed since I published some of my earlier work, a fresh look helped me spot mistakes and errors. In this way, I can see how creating a web folio gives one the incentive to display only their polished work.
As a whole, I really enjoyed the process of creating my web folio. I particularly enjoyed putting together the design for the Application Package and Best Works page. I found WIX's UI very intuitive in creating my designs, as I wanted my pages to be as visual as possible. One thing I found difficult was ensuring I struck a balance between welcoming, but professional in my writing. I wanted my homepage to feel warm and inviting, but without being too informal. Regardless, the process of creating the web folio was overall a wonderful experience.
Reflection on Strengths and Weaknesses
As Eng 301 comes to a close, I want to take a moment to reflect on my strengths and weaknesses in technical writing. As a starting point, I find that while I am able to be fairly clear in my writing, I sometimes struggle with using the passive voice rather than an active voice. This is still something I have to regularly monitor my work for. As well, I find writing well-structured and helpful peer reviews to be more difficult than I initially expected. While it is fairly easy to notice grammatical errors and formatting errors, I think my feedback falters on the more holistic aspects of my partner's work. This may be because it is more difficult to voice or pinpoint my criticism when attempting to give this type of feedback. It reminds me of the quote by Neil Gaiman, "Remember: when people tell you something’s wrong or doesn’t work for them, they are almost always right. When they tell you exactly what they think is wrong and how to fix it, they are almost always wrong." That is to say, sometimes I can intuitively feel when there is something to be improved in my partner's writing, but I find it difficult to provide specific advice on broader aspects of their work. As for my strengths, I think I did a good job on writing a technical definition for the term algorithm. I believe it is important to be able to simplify and articulate difficult concepts, and I enjoy the process of making bite-sized, digestible explanations for complicated phenomena.
Reflection on My Skills As a Student
I think my skills as a student play a significant role in my future vocation (ie. software development). First and foremost, many of my computer science classes reflect particular aspects of the software industry. For example, I took CPSC 210 this term, and I was expected to learn how to utilize the Java Swing library in a short period of time. This kind of rapid acquirement of technology is a useful skill when adapting to new work environments. As well, my professor for 210 often demonstrates OOP concepts through direct industry examples.
Furthermore, I find that although academic courses provide ample guidance, there is still a lot of self-learning required to be successful. The practice of self-learning and self-teaching difficult topics is essential to being able to learn new things later down the line, particularly in a field as fast-paced and changing as software development.
I also find that, as a student, I get a breadth of opportunity to develop writing and reading skills. My undergrad philosophy major and ENG 301 have taught me to communicate effectively in various environments. For example, the practice I gained from ENG 301 is directly applicable to professional writing in the real world (ie. writing memos, preparing resumes and cover letters, etc.). In this way, I think being a student prepares me to be well-rounded for my future career in software development.