The readings and responses listed here should take you approximately 60 minutes.
To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of this document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
1. Learning Fluency by Turing alum Sara Simon (30 min)
- Your key take-aways OR how you're going to implement specific points (minimum 3):
- The idea of fluency and how it applies to coding, programing and everything that comes with it is a language to become fluent in.
The assignments listed here should take you approximately 2 hours.
To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
Documentation of a langauge, framework, or tool is the information that describes its functionality. For this part of the practice tasks, you're going to practice digging into documentation and other reference material.
The assignments listed here should take you approximately 25 total minutes.
To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
Need help? You can go back to the files/directories portion of the lesson here.
The readings and responses listed here should take you approximately 20 minutes total.
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
- HTML's purpose on a webpage is to give the browser structural information, such as text or basic styling.
- An element is what you're calling inside the tags. It's what lives inside the angled brackets. An element would be
body
and the tags would be<body>
and</body>
. - Attributes give extra information to the browser.
- The head element gives the broswer information about the page, which often includes the title element and other meta information or links to your stylesheets. The title element will display what you put inside the tags on top of the page or within the tab for the page. The body element is meant to show what to display in the main broswer window.
- The keyboard shortcut to view the source of a website is option+command+u.
- The `` tag can go from 1-6 and is used for headers.
The assignments listed here should take you between 1.5 and 2 total hours.
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
The readings and responses listed here should take you approximately 50 minutes total.
To start this assignment:
- Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
- Click the Edit button when you're ready to start adding your answers.
- To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.
My knowledge of Git is small at the moment, but much greater than it has ever been. I was always very overwhelmed by the concept, but am starting to truly appreciate what it has to offer.
I learned that in the past, companies would really only use verysion control if they had the means to afford it. That is because they had to have massive servers to store, not just the snapshots that we have now, which are really only recording changes, but entire websites worth of code. Many, many times.
The basic pieces of code used in the terminal for Git are:
1 Starting a campfire | |
1.1 Prepare area | |
1.1.1 Clear debris | |
1.1.1.1 Figure out where you want to clear | |
1.1.1.1.1 Go to car | |
1.1.1.1.1.1 Get broom | |
1.1.1.1.1.1.1 Go back to area | |
1.1.1.1.1.1.1.1 Sweep debris away | |
1.1.2 Set ring | |
1.1.2.1 Decide what size stones you need |