In my Codeacademy course on How to Build Websites From Scratch, our positioning unit has concluded and we\u2019re now on to browser compatibility. Basically, we\u2019re going from using fixed dimensions of objects in websites to proportional and relative measures. This allows them to appear the same on different devices and browsers. In all honesty, it\u2019s one of those subjects that\u2019s boring but important.<\/p>\n
I am nearly caught up at this point, which to me is miraculous because we had another project to turn in for evaluation at the end of the last unit. I found the material to be challenging, and I encountered a real sinking feeling when I learned that I would have to build a static website using the unit\u2019s material and submit it for assessment.<\/p>\n
But I had also been equipped with tools to overcome this challenge. One set of tools, specifically, saved me from a night filled with hopeless frustration and instead allowed me to complete the project in just a couple hours without much confusion.<\/p>\n
That toolbox is brought to the world by Google Chrome and known as Developer Tools (or DevTools for short).<\/p>\n
In Chrome, if you\u2019re curious about any funky aspect of any website, you can right click on it and select \u2018inspect.\u2019 That will bring up a bar on the right side of the window displaying the various segments of code that your browser has translated into a sleek visual experience.<\/p>\n
![\"devtools\"](\"https:\/\/news.elearninginside.com\/wp-content\/uploads\/2018\/02\/screenshot-66-1024x576.png\")
For our assignment, we had been shown a version of what our site should look like, and we had also received a sheet with all the specs we would need to know. One could certainly recreate the existing website simply by looking at the end product and the spec sheet. But that\u2019s not what I did. Instead, I used DevTools to go in and check on all the fancy footwork the Codeacademy people used to create the site in the first place.<\/p>\n
DevTools allowed me to complete the project quickly and easily get unstuck whenever that occurred. Was I, at times, simply copying and pasting the code from the model to my own text editor? Absolutely. Did it matter? No.<\/p>\n
Sure, I wouldn\u2019t exactly be able to do this in a real world situation, but at the same time, I could certainly borrow fragments from websites that I particularly like and apply them to my own projects. This realization got me excited. Like, really excited. And the reason wasn\u2019t just that web development would be easier for me in the future.<\/p>\n
The excitement stemmed from the fact that, in the creative world, coding stands in its own field regarding how people reconcile it with intellectual property. If I were to copy and paste a company\u2019s logo, I should expect a cease and desist letter to land in my mailbox. If I were to copy sections of a George Sanders short story word for word, stick it in my own selection, publish it, and profit from it, I wouldn\u2019t just get a cease and desist letter. I\u2019d need to hire a lawyer.<\/p>\n
It\u2019s true, copyright law still certainly applies to anything created by computer programming, be it a software application, a website, or anything else. You don’t need to apply for it. If you have created something, it’s your intellectual property (unless you created it as part of your employment contract). I would not be able to copy the code of an entire website and push it as my own. But I can <\/em>see how a programmer designed certain aspects or created various features.<\/p>\n In one sense, this is no different from, say, creating a piece of visual art or choreographing a dance. Once your creation is displayed, people will be able, to a certain extent, see what you have done and how. But the presence of DevTools, along with the popularity of open-source sites and apps shared in places like Github, allows for an incredibly greater degree of collaboration.<\/p>\n","protected":false},"excerpt":{"rendered":" One could certainly recreate the existing website simply by looking at the end product and the spec sheet. But that\u2019s not what I did. Instead, I used DevTools to go in and check on all the fancy footwork the Codeacademy people used to create the site in the first place.<\/p>\n","protected":false},"author":11,"featured_media":4528,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[6],"tags":[6116],"class_list":["post-5142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-editors-picks","tag-learn-to-code"],"yoast_head":"\n