Two Scoops Study Session Part 2
Key point
This was a study session where participants read Chapters 1-3 of Two Scoops of Django together and shared practical application experience.
Details
We reviewed Chapters 1 through 3 of Two Scoops of Django together and organized the basic principles of Django development along with key points for practical application.
Moonsu summarized the content from Chapter 1 through Chapter 3 in a presentation, and after each chapter, Hoseong added real-world application cases and experiences from 8Percent. Q&A continued throughout, so the session went beyond a simple book summary and connected to an industry perspective as well.
Chapter 1 covered coding style following PEP8 and how to use tools like flake8 and isort. It emphasized organizing imports in the order of standard library, Django core, third-party apps, and project apps, using explicit relative imports, and avoiding import *.
Chapter 2 focused on how to reliably set up a Django development environment.
- Use the same database locally as in production to improve reproducibility and test accuracy.
- Separate dependencies with pip and virtualenv to manage the project environment independently.
- Keep a systematic record of changes using a version control system like git.
Chapter 3 covered how to structure a Django project. This is a topic where even core developers disagree, but it was noted that a configuration separating the settings root from the Django project root under the repository root is generally widely used.
It was also noted that using Cookiecutter makes it easy to set up an initial project structure, and that there isn't just one right answer for project structure.
Finally, the author reflected that the study session was a valuable opportunity to ask questions directly about things they were curious about as a beginner developer and get answers. After going home and running flake8 themselves, they realized that more code than expected didn't meet PEP8 standards, and resolved to keep practicing in order to write more readable code.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.