The key concepts are pretty easy to master across the board for both HTML and CSS for beginners. Remembering all the properties is a little more difficult. As a person who must have been out sick in the third grade when they went over colons and semicolons it was a bit more difficult than I imagined. I constantly forgot which one to use as I worked on styling different h tags. I would imagine one of the most confusing pieces is remembering all the different fonts it will accept as well as choosing and remembering different hex color codes.

Most of the time spent for me was trying to do edit the code from spelling errors and using the wrong punctuation. It brings me back to the first article I read on The Linchpen and the parallels between a journalist and a programmer. Unfortunately, for me I’m not a journalist nor do I aspire to be. As a person who tweets in fewer than 140 characters, often having to forgo punctuation it makes it a bit more difficult. For this very reason, I enjoyed the CSS part of the learning exercises.  It allows for clean code on the HTML file with just classes and ids instead of styling each h2 and div with repeat code over and over again.

As for how the Codecademy operates, it makes a lot of sense. I’m not sure how I would simplify it, but it seems a little heavy. I’m not sure if it will make it more difficult in the future, but I think it could do without the squares around the different properties to force memorization upon the students. The reading is a little heavy on the left hand side, but it does help in understanding. The only real complaint I have is that it often freezes and it wont let you input more code. Aside from that, it has really helped me understand many of the key concepts.

I’m beginning to learn that code can be layered, and that different languages will allow us to do different things.  Some languages provide the basic structures of a site, while others are markup languages and allow us to “dress up” the structure.  Understanding what language is appropriate for what I’m trying to do will be key.  I’m also starting to learn that coding, even with a markup language is going to require a lot of memorization and exercises in order to keep myself familiar.  Responsive web design is becoming more and more important, as I am almost more likely to view a website on my iPhone than on my computer.  And someone else might view it on their HTC phone, or a tablet of any size, or any variety of devices.  A website, not just an app built for a specific operating systems, has to be able to adapt to any device now, and look like it was designed for just that screen size, width, and length.  At first I’m probably going to have more success working with adaptive layouts, as these are going to be easier to make and more foolproof  from the start.  But once I become more comfortable, responsive layouts are going to be my goal.  It will be way easier to design for for just a few different layouts than hundreds, and I’ll be happy if I can make my website look great on and iPad and and iPhone to start, as these are the devices I see most people using these days.

The web inspector has been interesting to use thus far, but is showing me that I have a lot of work to do understanding what each type of code is capable of.  It really is like reading a foreign language at this point, and every type of content seems like it written in one that is different than the previous one.  I’m looking forward to be able to understand what I am reading soon.

The articles on HTML and CSS brought me back to my migente.com and myspace.com days. Changing background colors, fonts, adding boxes, and frames around photos was all the rage in my youth. Mostly on the HTML front, CSS and the curly brackets make my head spin but I think these articles made it clearer. The way I understood it is; you place certain qualities in a single style sheet and then you just reference certain portions of the sheet in your HTML document. By placing it in a separate sheet you don’t have to read two different styles in one document should you need to edit. This reminds me of the Zen of Python where you want to make things as simple as possible so that anyone can replicate or edit the document.

I really enjoyed the articles on responsive design as well as adaptive layouts.  When I worked at an agency everyone wanted to redesign the websites we made for our clients a few years back in a responsive layout. I imagine it was due to the amount of potential revenue it could drive as opposed to editing their current websites to create adaptive websites. The agency of course would recommend adaptive layouts should the client not want to redesign their recently designed websites. It makes a lot of sense for every website being designed from this point on to be responsive. The sites must be designed with mobile and tablet in mind as Internet usage increases among non-desktop devices. It really is a huge missed opportunity for so many local businesses. As I continue to brand myself as a social consultant that offers web services to local business this will be a big selling point that I’ve underused in my past pitches.

I found the Web Inspector article really interesting. I’ve used it before but I have yet to use the network tab and the files tab, which I will now start to use. I was so fascinated I also read the article on the “Dollars for Docs” project. It’s amazing to think that the drug companies make content very difficult to read to protect their relationships with doctors. It’s equally amazing that with a few keystrokes and clicks you can get a clear and easy to read document with all the information of your health professionals and the financial relationship with the drugs companies. The web inspector tool is the modern day Sherlock Holmes.

In the readings for this week, I was really enthusiastic about how hands-on the material is getting. I like the ideas that were presented because it relates my experience of writing with the experience I have from COBOL. Until now, they have been exclusive from each other; I can write well and I can code COBOL well, but I never really felt that they were similar or connected. Now I can see how the coding can be seen as writing, rather than my original belief that it is only mathematical at heart.

I love how McAdams talked about why she started with HTML and CSS instead of other programming that is more “program-y” and made the case that writers will see it as closer to their craft. I agree wholeheartedly, as I view pure coding as a puzzle, with logic, math, and a solution. The HTML and CSS works more like a foreign language that can be manipulated once you understand the syntax.

I really liked Ethan Marcotte’s piece on responsive web design, and I thought that he was very good at relaying information in an engaging way. I wanted to read more of his writing, and his book looks very informative, but I don’t think I would buy it because I expect to find all of that information from other sources. I thought the way that he described the process was well done, but when he added examples of what he was doing, piece by piece, made it incredibly more understandable. I also think he is funny because he wants to be an unstoppable robot ninja.

The slide show about the analogy of web design wasn’t as helpful to me, but I think that this was partly because you have already gone over the house analogy. The preceding list was really helpful though, as it brought the reasoning behind learning this stuff straight to the front.

This week’s readings seemed to drive the point home that we can truly become marketable when we learn to manipulate our web-based platforms effectively. To take it a step further, we are actually unprepared to join today’s labor force when we can’t do it effectively. Most authors this week covered HTML and CSS. However, while some advised to just understand these concepts, many more stressed the need to practice them regularly. Again, the concepts only vaguely apply to my line of work, but I do see how applicable they can be to so many other types of work. As an avid online news consumer, I definitely appreciated the concepts that guide multi-platform content. I enjoy visiting sites that display effectively whether I am on my computer, phone or tablet. In fact, it significantly impacts where I go for online content. Learning the processes for getting it all to display seamlessly has already motivated me to learn to do it well myself. It seems it is the only way to ensure my readers are happy with the content, and always willing to return for more.

I thought the readings were very helpful, and were able to teach both beginners and those who have more experience. The video of how the internet works was entertaining and it made me think about how the vast majority of people view it as an “omni-present cloud” that simply exists outside of normal laws of physics. It reminded me of how many people view the media as some intractable machine bent upon feeding itself, rather than the public service many journalists are trying to provide.

Having some experience with programming, I had seen many of the “laws” given about programming in the workplace. I thought they were funny at many times, and unfortunately violated quite often in the corporate workplace (which is another viewpoint of people seeing something as a machine rather than a helpful tool). I had never thought to compare those rules to my writing as a journalist, but unconsciously I think that I did regardless. One of the hardest to follow for me is: simple is better than complex.

I like the idea of thinking like a programmer in our journalistic writing, as that is the background for much of my thinking. I am the son of two programmers, and therefore I find programming logic to be, well, logical. I want to delve into the guts of some programming languages, because I am always interested in learning something new about computers. I think that we can always make the languages more efficient and more dynamic, and that means that we should always be learning and adapting to new advances. It is also imperative, to me at least, to know where the origin of these languages and computers came from. The history of it is the basis for how we learn what mistakes we made and what to avoid in the future. I think this also applies to journalism, and writing in general. We should always be striving to write better; to report better; to investigate better. If we don’t learn as we go, we will get left behind.