Time - Alex - Slack CLI

[codesrobertson]

Assignment Submission: Slack CLI

Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions.

Reflection

Question	Answer
How did you go about exploring the Slack API? Did you learn anything that would be useful for your next project involving an API?	I started by doing a lot of the wrong things, like trying to be punny and making a workspace called "Coronadies" before realizing that we were supposed to use our cohort's workspace. In future, I'll be checking the query results in postman before creating my variable names, to improve readability.
Give a short summary of the request/response cycle. Where does your program fit into that scheme?	Getting a request back from a server is a bit to me like chumming the ocean for Jaws, only to find him smiling at you before you send a bullet into the air tank in its mouth. The Slack CLI project gets information via requests, and then sends responses via commands from the CLI.
How does your program check for and handle errors when using the Slack API?	It uses case statements in slack.rb, as well as exceptions in receiver.rb methods.
How did the design and organization of your project change over time?	My initial sketches on the design of this project were adapted from the Solar System and Rideshare projects, but I didn't really get a chance to start working on the program until after Devin presented her wave one walk-through, at which point, I assumed that was the scaffolding we were meant to use, and so, did. From there, the design spurred on out of necessity, and I changed my slack.rb file (the case statement particularly), several times.
Did you use any of the inheritance idioms we've talked about in class? How?	In terms of inheritance idioms, I used class methods in receiver, channel, and user in the form of self.get_url and self.show_all methods.
How does VCR aid in testing a program that uses an API?	As I understand it, VCR aids in testing a program that uses an API by recording the initial request made by the API, and then running subsequent queries off of the information gleaned from that initial request (thereby saving copious amounts of cash for the company who commissioned the program and/or API use in the first place).