Alex-Tideman/gist:8a196cd7a24b6fcf03c0

## gistfile1.txt
1. Visual mockups, baseline views to have visuals of data, consistent formatting of HTML, trying different data types, use of Pry, pushing through until it worked (not walking away with bad code).
2. Dynamic snake_case JSON parser
  a. We knew we needed to parse the JSON but spent too much time trying to make it work for any key values instead of the specific values we knew we needed.
  b. I think in the future always keep in mind that you should keep it as simple as possible as long as it works, and go back and make it better later. Keep pushing forward and check off stories instead of making the first story as good as possible.
  c. I think we improved at keeping the focus on the finish line and pushing forward without getting stuck on one piece of functionality. We all worked together to bounce ideas off each other and that allowed us to quickly get through code instead of one person getting stuck without knowing what to do next.
3.
  a. Mockups, find_or_create_by ActiveRecord method, POSTGRES GUI (Postico) to see table data
  b. Working as a group for all of the base functionality, feature-driven development, pre-planning and user stories
  c. Weird server errors with curl
  d. Break up user stories into more granular functionality
4. Clear communication when everyone could meet and work. Breaking out extension/refactoring/display responsibilities once the base functionality was done.
	1. Visual mockups, baseline views to have visuals of data, consistent formatting of HTML, trying different data types, use of Pry, pushing through until it worked (not walking away with bad code).
	2. Dynamic snake_case JSON parser
	a. We knew we needed to parse the JSON but spent too much time trying to make it work for any key values instead of the specific values we knew we needed.
	b. I think in the future always keep in mind that you should keep it as simple as possible as long as it works, and go back and make it better later. Keep pushing forward and check off stories instead of making the first story as good as possible.
	c. I think we improved at keeping the focus on the finish line and pushing forward without getting stuck on one piece of functionality. We all worked together to bounce ideas off each other and that allowed us to quickly get through code instead of one person getting stuck without knowing what to do next.
	3.
	a. Mockups, find_or_create_by ActiveRecord method, POSTGRES GUI (Postico) to see table data
	b. Working as a group for all of the base functionality, feature-driven development, pre-planning and user stories
	c. Weird server errors with curl
	d. Break up user stories into more granular functionality
	4. Clear communication when everyone could meet and work. Breaking out extension/refactoring/display responsibilities once the base functionality was done.