eoneill23

Session 2 Readings and Responses

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 first main take-away that I have after reading this piece is that not everyone learns the same way and that should be considered a good thing. If everyone learned the same way, had the same sort of mindset, and consequently, programmed the same way, the tech industry and everyone who interacts with it would be worse off. Diversity is ex

eoneill23

Session 2 Practice Tasks

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.

1. Documentation and Googling (75 min)

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.

eoneill23

Beginner's Guide to Git

By Eric O'Neill

Git is a Version Control System (VCS) that allows a user to track changes to files as well as "go back in time" to see previous versions of the files. With those abilities, it is often used as a collaboration tool by developers around the world.

Github is a web application that hosts web applications and allows developers to upload or push files where they can later be downloaded or pulled by anyone who has access to the repository, allowing for increased collaboration.

Here are a few basic Git commands:

* pwd - Print working directory. Typing this command allows you to see where you are at within your computer's directories.

eoneill23

Session 3 Readings and Responses

The readings and responses listed here should take you approximately 20 minutes total.

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

eoneill23

Session 3 Practice Tasks

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.

1. Creating Files and Directories (10 min)

Need help? You can go back to the files/directories portion of the lesson here.

eoneill23

Checklist/Rubric

Part I: Creating Directories and Files; Initializing Git and Pushing to GitHub

• I named my directories correctly.
• I named my files correctly.
• I structured my files and directories correctly.
• I made one initial commit.
• I pushed my initial commit to GitHub.

eoneill23

Session 4 Practice Tasks

The assignments listed here should take you between 1.5 and 2 total hours.

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

eoneill23

1. Based on the PAIRIN results, I would say that my greatest strength is my work ethic. I base this on earning the Ace Achiever, which falls under both self-management and working to influence outcomes and gain mastery.
2. In an ideal world, I think I work best individually, where I can control all aspects of a project. I also have plenty of experience working in groups and enjoy that as well.
3. Based on the PAIRIN results, I think my greatest area of improvement is in the growth/agency section. I tend to have a fixed mindset about things, so shifting that mindset for Turing and into the job field will be an important part of my Turing experience.
4. I hope to leverage my strengths in the field of software development by utilizing my strong work ethic to get projects done on time, as well as learn new things when necessary to stay up-to-date. Additionally, being self-confident will help me push through times when I am unsure of things, and being a lover of justice will help me thrive in a team environment.
5

eoneill23

1. Empathy plays an important role in my life, just like it does in everyone else's. Being empathetic has helped me communicate better and have better relationships in my professional and personal life. An example of this is at a previous job, my boss was unhappy with how I was going about a task that she had assigned me. After sitting down and talking with her and realizing why she was upset and what I could be doing better, I was able to go about the task in a different way and accomplish it to the standards that she was expecint.

2. Empathy is a critical piece of building software. As outlined in the articles that were part of this assignment, getting out, interviewing people, and soliciting their feedback and insight helped bring to light things that designers never would have thought of. Looking at software from the viewpoint of the users and helps to build more accessible and usable software. For example, utilizing alt text when adding images to a webpage allows screenreaders to describe the image to u

eoneill23

Day 1

1. On a website, the purpose of HTML code is to structure the website by utilizing tags and elements.

2. An element directs the browser how to structure the page by utilizing an opening <> and closing </> tag with content in between the tags. Tags generally use an opening tag <> and a closing tag </>, and the characters within the angle brackets indicate the tag's purpose. For example <p> is an opening paragraph tag.

3. Attributes provide additional information to HTML tags. An attribute appears in the opening tag of an element and is comprised of a name and a value, which are separated by an =. An example of an HTML attribute is <a href="www.google.com">Link to Google</a>. "href" is the name and "www.google.com" is the value.

4. In HTML, the head element contains information about the page and it isn't displayed to the user. You will usually find the head element before the body element on a page. The title element is used in HTML to display content in the top of the page or within a