After learning from it, you need to consider all aspects. The following is the software practical course learning experience I compiled for you. You are welcome to read it. Please pay attention to more exciting content.
After Teacher Pan taught software engineering practice, I feel that I have a deeper understanding of the subject of software engineering. Software engineering is a science that values ??practical operations. For software products, it is nothing more than a few steps of product definition, design code, debugging and maintenance. It seems simple, but the actual operation is complicated and difficult. It is no more predictable and accessible than other industry products, so learning software engineering well will help you to engage in the software development industry in the future. Lay the foundation.
In the software practice course, we talked about how to effectively use existing resources for software programming. When it comes to software development, you can also use the post-post method to learn from other people's excellent code resources just like practicing calligraphy. Copying excellent software is an important way to learn software development. As a poem says: "If you are familiar with three hundred Tang poems, you can recite them even if you don't know how to write them." The same is true for software development. In order to truly master the skills of software development, "temporary posting" is a good way to start.
I always felt that since I write a program, I should rely entirely on myself. Only in this way can I have a sense of accomplishment and be my own program. However, this course taught me to properly learn from other people’s things. , is not considered copying. On the contrary, it can also improve efficiency and save time. This is really different from the previous view. The details are as follows:
“In software programming, borrowingism plays a great role:
1. Source code exchange is convenient.
2. The use of feasible example programs Big.
3. Learn from what’s already available and avoid detours. ”
However, there are ways to learn from other people’s work, and it’s not just blind plagiarism. Here are some mentioned ways:
1. Existing system: borrow a chicken to lay eggs, buy it and use it;
2. Book example: simply modify and use it directly;
3. Online or Internet help: help documents, official support;
4. Open software source code: linux apache eclipse...
5. Internet resources: forums, search engines, news groups
After borrowing from it, we need to consider multiple aspects, such as the specific function and completeness of the code, and also consider the quality of each borrowed thing. These must be considered from many aspects, but you cannot blindly plagiarize just because you can learn from others in software programming. When the code is put together, no one knows whether it will work well. If it gets messed up and the program plan is small, no one in the company can afford the loss.
The course also mentioned that you should practice it from beginning to end with a small project. In this way, you will have an overall understanding and can gain a lot of development experience. It seems that if you do not study this course, you will not be able to understand the mysteries of software engineering in depth. This course has played a role in promoting our in-depth understanding of this huge frontier discipline of software engineering. The above is a brief discussion I made on a short section of the many methods mentioned in this course. More knowledge lies in our own learning and experience.
I highly recommend