“This
document attempts to be a high-level view of the architecture of the World Wide
Web.” Once I read that I knew this was going to be quite a read. I have some
concept of what architecture means (and not just the stuff I learned from watching
How I Met Your Mother) but I was not
quite sure how I was supposed to use this term when it came to Web Design. From
what I can understand this writing
breaks up the World Wide Web into two groups; the human part of it and the HTTP
– or the technology used and driven part of the Web. What the HTTP part of this
information seemed to be talking about is algorithms; out of my depth when it
comes to technology but I’ve heard my more tech savy friends talk about how
important these are. I know this has something to do with the fact that
anything having to do with the Web is always going to be dealing with large
numbers. Therefore, the best written algorithms to deal with these large
numbers means that it will run better. That’s all I could really understand
though; I’m curious about this part of the discussion in class.
The
second reading was much more useful. I know many people in this class come from
a strong art and design background. While I do have some experience with graphic
design it’s nothing that I feel strongly competent on. Therefor, while I do
like the coding part of our classes, I always do find talk about graphic design
very informative. For instance; I found this reading very useful because I only
have a few ideas of where to begin when I’m first designing a website. I know
basic parts of websites, I actually knew about one size design and I’ve picked
up different design ideas along the ways but I was not sure how to actually
tackle starting a website. This gave me some good ideas. The different
navigation design ideas are good because I know if you can’t navigate a website
the thing is useless.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.