Recap and Feedback
We started with linked documents and followed the development of applications that share work between browsers and servers. Then we ran a walking skeleton and saw that difference in action: a counter changes browser state, while loading todos sends an API request and reads stored rows.
Working through the examples has given you a way to explore an application: start its services, follow a request, find the relevant files, and try a change. You have also used migrations to describe database changes and written tests to check expected behavior and catch defects. These are useful starting points to return to as we build more functionality.
If you still have questions about how all the pieces work, that is completely natural. We have met several tools without yet studying each one in depth. Take a moment to identify one connection you can now explain and one question you would like to explore further. Part 2 develops the browser code through components, state, requests, and navigation.
Reflection and feedback
0 / 5 points
Consider the following statements and answer them based on your experiences from studying the materials and working on the assignments in this part. When answering the numeric statements, answer them so that value 1 means that you strongly disagree with the statement, and value 7 means that you strongly agree with the statement. Please be as honest as possible when answering. The feedback will be used to improve the course.