Two Scoops of Django Study - 9

We looked at form patterns in Chapter 12 and best practices for template usage in Chapter 13 of Two Scoops of Django. The Korean edition (based on 1.8) and the English edition (based on 1.11) have different chapter orders, which can cause confusion when cross-referencing.

During the summary sharing session, we first reviewed form patterns based on Heejin's first summary. To keep input values clean, proper Form Validation must be applied to all inputs, and we reconfirmed that careless validation in the past makes data analysis and operations more difficult later on.

Next, Seonggwon's final summary covered ways to keep template management easier and more concise. At 8percent, Django Templates are generated directly with IUEditor, and the frontend is in the process of shifting to a React base, so templates haven't been deeply considered, but through this study we learned about better directory structure and usable template tags.

In the deep-dive session led by Namhong, several additional topics were covered.

• Safe / Idempotent methods: A method is considered idempotent if sending the same request multiple times produces the same result. OPTIONS, GET, HEAD, PUT, DELETE fall into this category, while PATCH can be used like an append operation and may not be idempotent.
• Reading Form Validation code: We directly examined library code and traced the meaning of each validation step to deepen our understanding.
• Django Debug Toolbar: We shared debugging experiences of finding and improving N+1 query issues.

In the wrap-up, we discussed what kind of studies we'd like to do next, with topics like frontend, basic CS, and data analysis coming up. Miju, who joined us, started in frontend as a non-major, so this book's backend best practices didn't quite match her interests, and we also felt that it's important to align study topics with participants' interests.