XeLabs/cs-self-learning
2
0
Fork 0
mirror of https://github.com/PKUFlyingPig/cs-self-learning.git synced 2026-06-23 18:06:56 +08:00
Code Issues Projects Releases Packages Wiki Activity

Update 6031.en.md

Browse source
This commit is contained in:
smxm 2022-10-04 13:13:26 +08:00 committed by GitHub
parent 7a38ec92e7
commit f214cf2336
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/软件工程/6031.en.md
View file

@ -11,10 +11,11 @@
The goal of this course is for you to learn how to write high quality code, and what is meant by high quality is to meet the following three targets: The goal of this course is for you to learn how to write high quality code, and what is meant by high quality is to meet the following three targets:
> Safe from bugs. Correctness (correct behavior right now) and defensiveness (correct behavior in the future) are required in any software we build. > Safe from bugs. Correctness (correct behavior right now) and defensiveness (correct behavior in the future) are required in any software we build.
>
> Easy to understand. The code has to communicate to future programmers who need to understand it and make changes in it (fixing bugs or adding new features). That future programmer might be you, months or years from now. You’ll be surprised how much you forget if you don’t write it down, and how much it helps your own future self to have a good design. > Easy to understand. The code has to communicate to future programmers who need to understand it and make changes in it (fixing bugs or adding new features). That future programmer might be you, months or years from now. You’ll be surprised how much you forget if you don’t write it down, and how much it helps your own future self to have a good design.
>
> Ready for change. Software always changes. Some designs make it easy to make changes; others require throwing away and rewriting a lot of code. > Ready for change. Software always changes. Some designs make it easy to make changes; others require throwing away and rewriting a lot of code.
To achieve this, the instructors write a book explaining many of the core principles of software construction and valuable lessons learned from the past. The book covers many practical topics such as how to write comments and specifications, how to design abstract data structures, and many parallel programming caveats. You will explore all of these ideas in the programming assignments. To achieve this, the instructors write a book explaining many of the core principles of software construction and valuable lessons learned from the past. The book covers many practical topics such as how to write comments and specifications, how to design abstract data structures, and many parallel programming caveats. You will explore all of these ideas in the programming assignments.
In the 2016 spring, the course open-sourced all of its programming assignments, and the textbook can be found on the latest website (see links below). In the 2016 spring, the course open-sourced all of its programming assignments, and the textbook can be found on the latest website (see links below).