Lessons learned!

Q: What did you learn about team or large project development? What will you start doing, keep doing, or stop doing next time?

Yuze:

Things to start doing:

Deeper Understanding and Application of Documentation: I realized how important it is that I need to fully understand the documentation for the language of need and frameworks before programming. In future projects, I will first spend more time reading and understanding the documentation and mastering the basic tools to reduce technical debt and increase development efficiency.

Planning and Designing Ahead: Before writing code, I will start with more comprehensive planning and design, including the design of the data model and system architecture. This will help reduce the need for later refactoring.

What I will keep doing:

Maintain Code Quality: I will continue to focus on code quality, following SOILD principles and other best practices. This includes writing clear, easy-to-maintain code and conducting regular code reviews.

Team Communication and Collaboration: I will continue to keep communication open with the team and work together to solve problems. Teamwork is critical to the success of a project, and I will strive to be an effective team player.

Things I will stop doing:

Avoiding "shortcuts": I realize that using so-called code "shortcuts" often leads to poor code quality and difficult maintenance. In future projects, I will avoid this practice and focus on writing clear, testable code.