The process of coding a web page has definitely opened my eyes regarding the relationship between writing for print and writing for web and how they both differ and intersect. When it comes to the intersection between the two, I think a lot about how both writing for screens and writing for print involve clarity, conciseness, and knowledge of your audience. When it comes to clarity from web design, it’s important to think about whether or not the person reading your code can understand it. A question one can ask themselves and I frequently asked myself as I was cleaning up my code was, could someone go into the source and see what I actually did? Or is it too convoluted? For me, that involved deleting lots of code that I didn’t need from our demonstrations in class or even something as simple adding extra line spacing. The result, I think, was a clear project where someone can see what I did and how I did it and then go on to a Firefox Developer or whichever browser and find the source, and if they wanted to, copy it. I think this is a little different from writing for print, however. Because of the open source nature of the internet. No one can look behind the scenes of a book and see what went into writing the story, that is, there’s no HTML Source for the brainwaves of the author. This is I think the biggest contrast with web design and writing for print. On any website on the internet, I can go into developer source view and look at exactly what the web designer wrote, and likely even copy and paste it if I so well please. There’s no real comparison there between print and web design. That isn’t to say that print and web design are different though. I think the primary instance in which they are similar involves audience. We’ve discussed a bit in class about human centered design and I think both writing for print and writing for web have this in mind. Knowing your audience is so important to creating a project, whether web design, or print, without truly knowing your audience, you will fail.
2.) I’m actually super comfortable with my project at the moment. I think my computer widescreen view looks professional and I think I would be comfortable showing that to an employer. If I could do something differently, I would have like to have added a border but after some final hour experimentation I couldn’t really get it to go without messing everything up or gelling with the previously established style of my project. I only really was able to make changes to my CSS last week, before running into the same problem again so it kind of felt a little rushed, honestly, but I think my widescreen format looks great. Mobile leads some experimentation to be desired, but it is clean and professional. I’d say my widescreen format is very solid and I made some changes to colors and fonts and I think it feels more streamlined now.
When I think about my progress to this date in coding, I think of the idea that progress isn’t linear. I’m of the belief that no one really gets 5% better at anything each week when trying to learn something new or improve, rather one goes through ebbs and flows until they make a significant jump in competency. But, the person needs to put in the effort to make sure that when that jump happens, they are in position to take advantage of it. It applies so much to my experience in this class. I struggled mightily up until conferences and wouldn’t even want to look at the site. After our meeting and the discussion of parse errors and end brackets and how many random end brackets I had, I kind of had my jump. Everything clicked and the changes I had made to my site were realized, since while none of my changes were happening because of my parse errors, I kept adding the code that we learned.
How do I feel about my competency now? Well, before like Week 7, I was no better at coding than I was when I started and I was dreading the due date for this project. Well, here I am and I can say that I feel comfortable enough that I am not dreading the next project’s due date. Progress.