Toll Lanes: Design Reflection

The questions below are due on Monday July 26, 2021; 11:00:00 AM.

You are not logged in.
Please Log In for full access to the web site.
Note that this link will take you to an external site (https://shimmer.mit.edu) to authenticate, and then you will be redirected back to this page.

As discussed in the readings, good code is ready for change: it can be easily adapted to new purposes as program requirements evolve.

In 2-3 sentences, describe one aspect of your toll lanes code that makes it ready for change, and give an example of a change that it could support. (This example could be a new, different question you'd be able to ask about the toll lanes.)

Or, alternatively, give an aspect of your code which is not particularly ready for change (that's fine—there's always plenty like that!) and describe how you might make it more adaptable.

Formatting Help

Good code also avoids repeating itself. Since the exercises this week were related, there was opportunity to pull out reused code into helper functions. In ~1 sentence, describe one helper function you called multiple times. If there is no such function, consider refactoring your code to make one.

Formatting Help

So we can offer suggestions/feedback on your design, please upload the file containing your answers to all of the toll lane questions. This includes any extra code written to answer the analysis questions:

No file selected

Next Exercise: Survey

Back to exercises