Just when I thought there were no more professions that could be thrown into the talk of web design, an architect makes an appearance. Very early in the article says, "The document is written for those who are technically aware or intend soon to be, so it sparse on explanation and heavy in terms of terms." I consider myself in the group of soon to be with the little experience I possess and was intimidated when I read it being heavy in terms. 

In the article it is said that, "Principles such as simplicity and modularity are the stuff of software engineering" which with my experience of watching my friend, who is a computer science major, create programs I can't agree with this anymore. His advice to me regarding any coding I do is to make it as simple and easy to read as possible. Not to try to do too much with certain commands and to explain to yourself in your code what each line does. This will help you in the future to not break previous lines of code as well as help you navigate is something does break.

I am still confused about what a URI is. The article says all language use URIs which allows things written in one language to be referred to things written in another language. So is this just a translator? Or is there much more to it, where you must look at each line then decipher it yourself then be able to use that same string in another language?

Human-readable information is what I am most looking forward to doing with web design. I find myself to be a very creative person with graphics and organization of information. I understand the importance of the machine-understandable data to my goals.