Update API definition #73
Conversation
|
One note for the group to think about: I feel like this update does a lot of work to clarify that broader meaning of the term API. There's a part of me that thinks that's really important and I'd like our students to understand that nuance of the term, but if ultimately that makes this concept more confusing and students aren't really walking away with that understanding then maybe we just drop it and only talk about web APIs? I kind of hate taking it out, but it definitely might be the right move. |
|
@s-espinosa It resonates with me that leading with the broader nuance of the term API may be confusing for students. Perhaps starting out with web APIs as a foundation for understanding the concept may be easier to digest. To take the example out of context to illustrate my point. When I taught students about woodworking if I were to give a lecture about wood as a material my first example of types of real world wood would not be leaves, though the point could be peppered in as something for future thought. Also please let me know if slack would be a better place for this conversation. |
|
Anything that seems like it's too much to digest for an intro to apis lesson might be better suited for our follow up lesson: https://github.com/turingschool/backend-curriculum-site/blob/gh-pages/module2/lessons/api_consumption_in_ruby.md |
@BrianZanti I drafted some additional language for the intro to APIs lesson based on some feedback we received in the mentors channel (here).
I'm going to go ahead and drop a link to this PR to get some additional feedback on these changes so there will likely be a few more changes before it's ready for your review, but ultimately want to make sure you have an opportunity to weigh in as well.