Skip to content

Instantly share code, notes, and snippets.

View foxwellm's full-sized avatar

Matthew Foxwell foxwellm

View GitHub Profile
<img width="1549" alt="Screen Shot 2019-04-15 at 8 24 19 AM" src="https://user-images.githubusercontent.com/34201608/56140499-46bc0a00-5f58-11e9-9858-5a82fdc04bec.png">
1. Not working a crappy job again.
2. Know that others have gone through the same process, and that there is light at the end of the tunnel.
3. Attend mod 5.
4. Over slack.
5. Good support for junior dev.
6. Haven't felt I could do both Turing projects and jobsearch at same time.
7. Resume/ cover letter reviews
8. No
Project: Pic your landmark
Group Member Names: Matt Foxwell, Heather Hartley, Justin Clark
# DTR: Define the Relationship
Use this template to when conducting DTR with your project partners. *It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.*
### Guiding Questions to Define The Relationship:
@foxwellm
foxwellm / code-review-checklist.md
Last active December 10, 2018 18:42 — forked from JustinD85/code-review-checklist.md
Code Review Checklist

Would like reviewed:

  • https://github.com/JustinD85/jeopardy
  • How can we improve transitioning from clue -> wager -> answer -> answered when someone clicks a clue

    Make sure max value aligns to spec, consider popups instead of creatind it inside the squares.

  • Does the flow of the game make sense?

    Not applicable at the current state of the game. Testing functionality is their current position.

  • Suggestions for next steps

    Clear answered questions/ implement rounds/ create more visually appealing UI/UX.

  • Improvements where we could possibly use a utility function to shorten overall code length, maintaining readability

Consider using class inheretence rather than utility functions to better achieve learning objectives.

@foxwellm
foxwellm / code-review-checklist.md
Last active December 10, 2018 18:43 — forked from thatPamIAm/code-review-checklist.md
Code Review Checklist

What we would like reviewed

where would you see places where JQuery would help? How's our classes looking, planning on using DailyDouble Class and then Round3 as a sub class. Any unintuitive gameplay that glares out.

5 mins

  • Get together with your group and send a link of your team's GitHub Repo to the pair that is reviewing your project.
  • Look over this guide with your project partner and highlight the pieces where your team can use assistance/you would like your reviewers to take a closer look. Fork this gist and send the forked copy over to the pair reviewing your code.

45 mins

Why do package managers exist for front-end developers building web apps?

Building web applications across multiple platforms (IE, Firefox, Chrome, Safari etc), front-end developers can run into issues where code can run on one platform, but not others. There can be packages that are tailer fit to fixing an issue that they may run into that solves the problem which has been made by other developers who ran into the same issue. Because each package is tailer fit to solve one particular issue, package managers are used to allow you to customize all the packages you require, without having to download the massive library of all the packages out there and more importantly keep them up to date when a developer updates their individual package. The package managers are also valuable when working on group projects as your whole team will have access to the custom package set that has been created.

What is npm and what does it allow developers to do?

NPM is a package manager (Node Package Manager) that is cu

  1. What drove me to come to Turing was the self-realization that I should be doing more with my life. I definiteltly did not take school as seriously as I should have when I was younger and although I regret it, it's helping motivate me now. My Pairin themes definitely focus on me being a quiet and solitary person, but I think the team projects in this mod have helped me expand on that and have helped me grow in that regard. The Turing talks held in Clarke with past Turing grads have helped me see a place in the tech industry, their stories of how they knew nothing before coming to Turing and how well they're doing in the industry now have shown it can be done and helped allieviate a lot of the anxiety.

  2. It was difficult telling my story because there is defifnitely a large act 2 filled with failure and it's not fun telling people about it. I think just telling it more will help overcome the negative feelings and the act 3 will feel that much better in telling.

What have you learned about the use of agile vs. waterfall in software projects? The main takeaway is that agile can be more flexible while making a project in that it is more responsive to any changes that can or should be made.

How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)? We tried implementing an agile method of getting feedback from one of our three different instructors (trying to rotate between them). The hope was that they would bring up a point that maybe we were heading in the wrong direction and we could course correcrt before going too deep in one direction.

What role did you take on in the project? Myself and one of the other two teammates were definitely storming and butting heads early on, but I think towards the end of the project I took on more of the leader position solely because I had the most knowledge of how to tackle the more advanced problems the project faced.

What changes wo

Gear up

Having a good sense of empathy helps in understanding what someone else might be going through, in a way putting yourself in their shoes. It's very important when communicating with people from all different backgrounds. This comes into play when designing software because you aren't always designing software for someone such as yourself, but often times for a group that has unique requirements that you may have never knew existed before. Empathy is important on a team because to get everyone’s input for an idea, you must be able to fully able to understand what everyone is trying to get across. I find it difficult to be empathetic in professional settings when someone is being forceful about their input and not considering what others have to say. I think to improve, I should start repeating their points first, so that they know I have been listening and understand the points they are making before adding my own input that I feel would make improvements.

  1. Say "I don't know".
  2. Absorb massive criticism with ease.
  3. Be capable of writing bad code.

As someone who is starting this journey as a coder later in life, I realize I am behind in terms of general knowledge as someone else the same age as me. However, what gives me great hope for this field is that the technology and software is ever changing and therefore once the groundwork for understanding how one software works is understood, it will be translatable to any new software that comes out. But first I need to get to understanding the foundation, and to do that I need to set ego and pride aside and learn as much as I possibly can in a short amount of time as possible to achieve that. To do this I need to be a student long after I have left Turing, learning from as many people as I can willing to teach me.

Checklists provide an easy way to make sure the basics aren't overlooked, it can be very easy to overlook things when you become overconfident in what you are doing to miss something very simple.

Day 1

Chapters 1 and 2

  1. On a website, what is the purpose of HTML code? HTML describes the structure of pages on a website
  2. What is the difference between an element and a tag? Elements are made up of two tags, an opening and closing tag. The element tells the browser something about the information that sits between the opening and closing tag.
  3. Why do we use attributes in HTML elements? Attributes provide additional information about the contents of an element.
  4. Describe the purpose of the head, title, and body HTML elements.