Sacha Sedriks artificialarea
| Object Drills | |
| re: https://courses.thinkful.com/nw-fund-v2/checkpoint/7 | |
| -- | |
| Pair'd: Sacha Sedriks (me) & Nathaniel Mata | |
| 1. Object initializers and methods > DONE | |
| https://repl.it/@artificialArea/drill1object-initializers-and-methods | |
| 2. Iterating over an object's properties > DONE |
| Higher-Order Function Drills | |
| re: https://courses.thinkful.com/nw-fund-v2/checkpoint/6 | |
| -- | |
| Pair'd: Sacha Sedriks (me) & Khandaker Sultana | |
| 1. Functions as arguments (1) > DONE | |
| https://repl.it/@artificialArea/drill1Repeat | |
| 2. Functions as arguments (2) > DONE (failed Bonus Credit. revisit?) |
| Per assignment: https://courses.thinkful.com/interactive-web-apps-v1/checkpoint/2 | |
| -- | |
| "In this document, jot down at least 5 questions that you have about jQuery and interactive web apps so far. As you work through the rest of this module, see if you can find the answers to each of your questions. If you get to the end of the module and still have unanswered questions, be sure to share them with your mentor." | |
| -- | |
| Preface: No questions yet. But will be sure to update when they arise... | |
| -- | |
| Q1: |
| Per https://courses.thinkful.com/interactive-web-apps-v1/checkpoint/5#assignment | |
| "For the 3 remaining user stories (add items, check/uncheck items, and delete items), | |
| plan out each function in pseudocode (plain language)." | |
| See: https://repl.it/@artificialArea/shopping-list-v23-Pseudocode-assignment |
| -- | |
| Greybox Wireframe: | |
| https://artificialarea.github.io/thinkful-quiz/greybox/ | |
| -- | |
| Flow Diagram: | |
| https://github.com/artificialarea/thinkful-quiz/blob/master/greybox/back-of-napkin.png | |
| -- | |
| Content: |
| -- | |
| Live Site: | |
| https://artificialarea.github.io/thinkful-quiz | |
| -- | |
| Repo: | |
| https://github.com/artificialarea/thinkful-quiz | |
| -- | |
| Per assignment: |
Pairing: Sacha (me) / Jerrad / Brian Per: Thinkful's 'How web apps work' Assignment
In terms of communication protocol, I quite like the analogy as described here, in which the 'request and response' between software, devices, etc is analogous to the communication protocol — syntax, semantics, and timing — of when two people greet each other.
In this scenario, first person to intiate contact is akin to the client, while the other person is the server. The client gestures to get the attention of the server and subsequently asks/requests something ("Hello. What's the situation with x?"). The server receives the request and provides a response, which the client then receives (`"There are several things I can tell you about
Pairing: Sacha (me) / Jerrad / Brian Per: Thinkful's 'Reading API Documentation' Assignment
Visit the meetup.com API docs...
Yes. Need to obtain member autorization an an access_token in an Authorization header prefixed with bearer.
e.g. curl -H "Authorization: Bearer {access_token}" https://api.meetup.com/members/self/
--
doc: https://www.meetup.com/meetup_api/auth/#oauth2-resources