Self Evaluation Piece

The composing process of this final revision process started during my conference with Andrew, during which he gave me a lot of ideas that I could build the foundation for my revision on. We agreed that an article would be a good genre for the revision, and so I thought of ways that I could turn my formal midterm research report into a less technical and more informal article. To see what aspects an article should include, I used the website http://www.procopytips.com/write-newsletter-articles, which lists seven steps for writing an engaging newsletter article. For the article, I had to identify an audience, an issue, and a call to action. The audience was very obvious as my midterm focused on a group called Python for Beginners, so my target audience was the members of that group. The issue was that the name of the group is misleading because it does not cater to the needs of inexperienced people who are just starting out Python programming. I know this firsthand from my case study, which I used to recount my experience and explain the problem that I ran into as a beginner who was misled. For my call to action, I proposed two solutions that I thought would improve the usefulness of the group for actual beginners. When actually writing the article, I made sure to use active voice and to turn down the formality in order to keep my audience interested. I started out by introducing the topic and the events that led me to joining the group. I narrated the problem that I ran into, how I misjudged the knowledge threshold for participation in the group, as I am sure many other beginners have. Then, I proposed a possible solution to alleviate the problem and the benefits of implementing that solution.

“Success” for my own project would be making my Midterm more interesting for its intended audience because if it gains more support, there is a bigger chance that people will put my proposed solutions into effect. I think the writing choices that I made in this piece that were most successful were my use of personal experience to identify a problem and how I transformed my writing from something technical and formal to something more engaging. I wrote about my experience so that others who have experienced the same thing can identify with me so that I can make a connection with them. Hopefully, this connection will make it more likely that they will support my ideas to improve the group, making my proposals more likely to be acted upon. My original Midterm project was written in a very formal tone, whereas the revision was more compelling by using relatable experiences. This approach of using personal, relatable experiences is very helpful in building a stronger relationship between the writer and the reader, which I will definitely continue to use in future writing tasks because it keeps the interest of the reader.

The least successful part of my article, in my opinion is my lead. It’s a very weak beginning to the article because there’s a lot of introductory material that delays the raising of the issue to almost the middle of the article, this creates a lot of waiting for the reader to get to what the point of the essay is. I included the introduction/background information because I felt that it was important to have in case someone outside my target audience (someone not in the group or even someone who has never heard of Codeacademy). An outsider would need some explanation as to what kind of situation is at hand. If I had more time, I would have tried to reduce any excessive background information that’s irrelevant to the problem of Python for Beginners not being beginner-friendly.


Kari's Portfolio

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License