Response One

Coding has made me rethink the way that I see writing. Not just in terms of technical aspects such grammar or the concepts that I’m referring to, but the content of the writing itself. It seems as though people often (and I know that I am guilty of this) word-vomit onto a document, write everything that comes to mind, and fail to consider their audience. When you code, everything that you do has a purpose. Every tag you use, header you make and section you include is there for a reason. Certain aspects of the CSS are extremely calculated in order to have the best visual appeal, and to do this successfully usually requires a lot of trial and error. The words that we use should have the same exact importance to us. If we want people to look at our work, pay attention to it and actually absorb the message of the writing, there needs to be a reason for the decisions we make about that writing. I see a lot of this need to be clear with words and phrasing when I am working on an article or copyediting for The Hawk. When I am faced with a shorter word count than expected, everything that I put into a story needs to be a value-add to my story. I only recently drew this parallel between coding and writing for the school’s newspaper, and the similarities are striking. Not only is this applicable in that particular setting for me, but I also find that when done correctly, coding’s exactness and effectiveness for communicating (for those who understand the language) is unmatched and doesn’t disguise itself as something that it’s not. This concept is what makes me think differently about my writing, as I strive to make the things that I write as clear as possible to as many people as possible. And while this may require time to sit down and revise what I’ve already done, it is something that is necessary to be clear to my audience, just as we practice clean coding to make the most technical side of our work as readable as possible.

Response Two

Throughout this semester, I think that I have maintained a steady level of progress on my work. As of now, I think that my resume accurately reflects what I am capable of doing with HTML and CSS and looks professional, which is what I was hoping for. Although there are still some elements in my code that I’m not sure I fully understand, such as padding and margins, I think I have utilized my resources to the best of my abilities for now without going to open coding hours and having those things further explained to me (although this is something I am planning to take advantage of in the upcoming weeks). If I had extra time to practice coding and work on my resume throughout the past few weeks, I think I might have been able to better grasp those concepts and potentially try changing some other things on my resume that I think might make it more visually appealing and engaging to a reader. As far as what I do understand with coding, however, I am very comfortable. The more time that I have spent reading my code as well as my classmates, the less complicated it becomes. Even when I actually do spend time working on my HTML or my CSS, things usually click for me after a few bits of trial and error, and the more I do it, the more natural it becomes. Moving forward, I would be hesitant to tell a perspective job that I am proficient in HTML and CSS, just because I currently feel like I need more practice with it. However with the way that things have been going for me with learning different elements of code and understanding how they work together, I think that by the end of the semester I would be confident enough in my abilities to bring it up with a potential employer and show them my website as a reference.