Peer Code Share

Option 1

Diagramming:

For the API consumption portions of your project, draw a diagram of how your classes interact. There are many ways you could go about this. If you Google “Class Diagramming”, you will probably see very in depth diagrams including “UML (Unified Modeling Language)” diagrams. You don’t need to go as in depth as UML. Your goal is to create a diagram of what classes you have and how they interact.

Share:

Share your diagram with a partner. Give them a chance to look through the diagram before you explain it. Don’t look at code just yet.

Discuss:

With your partner:

• Is the diagram clear? How could you make it more clear?
• Look at the code that goes along with the diagram. Do the two match up?
• Is the code readable?
• If something were to change (for example, we switch our current API to a new API), would the code be easy to change? Would it be easy to add on to the code?
• How could you improve your code organization for the API consumption portion of the project? How would this change your diagram?

Option 2

Presentation

Presenter: Each student will present on the organization and process for completing one of the consuming the API endpoints user stories. Talk through why you made the decisions and less about how the code works.

Reviewer: As a reviewer you should provide feedback and ask questions. Things to consider as a reviewer:

• Is the code readable?
• If something were to change (such as switching the API) would the code be easy to change?
• Is the organization of the code easy to follow or understand? Could a new developer add on to the code easily?
• Is there any opportunity to improve code organization for the API consumption portion of the project?

Reflection

Once everyone is finished presenting, take a moment and create a gist or document with your take aways from the Peer Code share. Please then share these with your instructors via DM.