You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use this template 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:
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that you’ve completed the tutorial, take a moment to write a reflection on your experience to help solidify what you’ve learned.
Brief summary of what you researched
I researched GraphQL, which is a different style for building an API.
GraphQL uses a single endpoint and a strictly-typed schema through which all requests are sent.
The schema defines the resources available for retrieval in addition to the accepted parameters when fetching the data.
Typical REST APIs require loading from multiple URLs (endpoints) that can over or underfetch data and requires the client to know the exact location of each service.
GraphQL APIs obtain all of the data that an app requires in a single request (endpoint) and has the capability to allow clients to define the shape of the response for each request (i.e. what information is sent back to them).
This gist contains a short assignment we'd like everyone to complete before our formal lesson.
The prework involves reading some of the React Router documentation, and will allow us to keep the lesson more hands on.
Instructions
Fork this gist
On your own copy, go through the listed readings and answer associated questions
You will not be turning this in; it's for your own understanding/learning/benefit 😁
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create a GitHub gist to answer these questions in as much detail as possible. Imagine someone is asking these questions in an interview (these are popular interview questions).
1. What is a "data model", and how does it relate to the DOM in a front-end application?
A data model is what holds onto the state of our application. It is a single source of truth for what
should display on the page. An example of a data model could be an array of objects.
2. What is a "framework?" And how does it differ from a "library?"
A framework provides a standard way to build and deploy applications. It is a universal, reusable software
environment that provides particular functionality as part of a larger software platform to facilitate
development of software applications, products and solutions.
CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!
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.
Purpose
You will be a contributor in several paired/group project throughout your Turing career working on complex technical challenges. You may be surprised to find out that < 1% of failing projects at Turing are due solely to technical definicines - in fact, the majority of failing projects are due to intrapersonal/team issues. In order to set yourself (and your teammates) up for success, it is critical to clearly communicate and set expectations with your teammates.
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.
Please use the following gist to capture your thoughts, goals, priorities, etc. as outlined by each question. You will be using these questions to help give your mentor a better idea of who you are and want to become as a developer! Please note, this is meant to be a starting point for building your norms with your mentor - you may need to adjust scheduling expectations, communication expectations, etc. when you start working with your mentor!