ericquayson
commented
9 years ago Journal, Week 6
Keep writing! Tomorrow you should have your final draft of your Resource journal and rough drafts for your Reflective and Tutorial journals.
Reading APIs: Etsy
Here's another batch of questions to guide your research on the Etsy API. Chances are high that you'll get asked these questions in class tomorrow or that you'll need them for your homework.
- What Resource in the API represents...
- an individual product?
- a group or collection of products?
- images associated with a product?
- sizes and colors for a product?
- What actions and endpoints exist for each of these Resources?
- What parameters do each endpoint require or accept?
- What fields are returned for each Resource, specifically:
- an individual product?
- a group or collection of products?
- What additional fields can be requested for each?
Shaping Up With Angular JS
Last night was a (very) quick tour of the course. Tonight is reinforcement: play through (as in, try to complete without help) levels 1 and 2. You've got a lot to do tonight, so don't spend too much time here. If you get stuck, buy the answer and move on. Tomorrow you'll do the same with levels 2 (again) and 3. It'll come back around.
For Your GitHub Only
Keep building your Responsive GitHub page. Tonight, try to get the mobile view done. After merging, cut a new release--* branch from master and a new branch from that called feature--responsive-mobile.
Etsy Goes On
Elect a single Team Lead for tonight. Formulate a group plan of attack for building out at least one feature per person with HTML, (S)CSS, and some Angular JS placeholders, but with one catch: the Team Lead cannot write / commit any code. His or her job is to pair up with each of the other two, lead code reviews, and ensure the submitted work matches the joint plan. That person also has work to do outside of this project, so resist the temptation to make a ton of headway at the expense of your team.
The Team Lead role will rotate, so you'll definitely get a chance to be one. If that's you this time around, don't waste your time waiting around for code to review: refine the plan, document the API for the next phase of development, pro-actively pair up with your teammates, help with research... make the most of your time to maximize their productivity.
Your big goal as the whole team should be to start caching some data from the API using curl or Postman. Let's see, last time we put that data in apis/github/... Where do you think it should live this time? Did you guess apis/etsy/...? You're right! Make the local filesystem path match the resource URI as much as possible to make the transition to real API data as easy as possible.
USERNAME.github.ioTIY-GitHubfor features and releasesTIY-Catalogforfeature--*intodevelopUSERNAME.github.io:journal-week-6TIY-GitHub:release--*-- if you're ready for another releasefeature--*-- for any new featuresTIY-Catalog:feature--*-- for any feature you're working on