A simple reflection about the main lessons learned while building the DevJournal project.
Building DevJournal helped me understand Django better.
At first, many parts of the project looked separate. Models, views, templates, URLs, forms, and settings all had their own role. After more practice, it became easier to see how they work together.
One important lesson is that models are the base of the project. They describe the data. If the models are clear, the rest of the project is easier to build.
I also learned that views are not just functions or classes. They connect the request, the database, and the template. A view decides what data should be shown to the user.
Templates also became more clear. They are not the place for complex logic. Their job is to show information in a clean and simple way.
Another lesson is that small steps are better than big changes. When I changed too much at once, it was harder to find mistakes. When I worked step by step, debugging was easier.
Git was also very useful. Commits helped save progress. They also made it easier to understand what changed in the project.
I learned that deployment is a separate skill. A project can work locally, but a real website needs more setup. It needs Docker, a database, Gunicorn, Nginx, a domain, and HTTPS.
The project also showed me that mistakes are normal. Errors are part of learning. Each fixed error makes the project and the developer stronger.
DevJournal is not perfect, but it is a real step forward. It helped turn theory into practice.