Time Travel: 2014

The reason why Lin Hui was discouraged from reading the books he introduced later was not because the content of the books was deceptive.

On the contrary, these books are rich in content and realistic in description.

But it is precisely because of the truth that it is easy to break the beauty in people's hearts.

The above books objectively reflect three super troublesome things that a programmer faces in his career:

——Document writing, software maintenance, occupational diseases.

This point about occupational diseases is easy to understand.

After all, programmers often face intense computer work, and staying up late is commonplace.

These may not be very discouraging to a person who is interested in working as a programmer. After all, many professions have occupational diseases.

"Software maintenance" is the real killer.

The most intuitive and well-known form of software maintenance is debugging.

But debugging is far from software maintenance itself.

Software maintenance is far more complicated than debugging.

After the software is put into operation, some errors that were not discovered during the testing phase may be exposed, and corrective maintenance is required to correct these errors.

Due to changes in the external environment (software, hardware) and data environment in which the software runs, the software needs to be modified to adapt to these changes, which requires adaptive maintenance.

User needs are constantly changing. In the process of using the software, users will put forward new functional and performance requirements for the software. In order to meet these new requirements, the software must be modified to improve its functions and performance, which requires perfection maintenance. .

Using advanced software engineering methods to redesign, code and test software or parts of software that need to be maintained to improve the maintainability and reliability of the software and lay the foundation for further improvement of the software in the future is called Preventive maintenance.

In addition to these, there are a lot of messy maintenance...

It can be said that after a software is released, programmers' daily work is either maintaining the software or on the way to maintain the software.

And the work involving software maintenance is very troublesome.

When debugging, everyone looks forward to standard comments.

When writing bugs, almost everyone forgets to comment.

Some copy-paste bastards also like to make it into a "black box" and blindly encapsulate it.

Lots of troubles.

Although this is troublesome, software maintenance is a technical matter after all.

As for technical matters, this is part of the programmer's job. Although such things are troublesome, they are also obligatory.

What bothers programmers the most is the endless variety of documents, and software development documentation is one of them.

I am a programmer with a bachelor's degree in accounting/software engineering. I can write endless documents when it comes to work or study.

In his previous college life, the biggest impression that Lin Hui had on him during his sophomore and junior years seemed to be the endless lab reports and various messy documents, which were very annoying.

(…I don’t know what the specific situation of online classes has been in recent years)

After work, there are endless documents.

Take software development as an example:

At different stages of software development, different documents need to be written.

In the planning stage, detailed design documents, unit test plan documents, integration test plan documents, etc. need to be written;

In the development stage, although there is no need to create new documents, you still need to deal with documents, and programmers need to modify previous documents;

During the testing phase, unit test reports, integration test reports, system test reports, etc. must be written;

During the software release stage, installation manuals, user manuals, upgrade instructions, etc. must be written.

When it comes to installation manuals and user manuals, they should be as easy to understand as possible.

Well, although many software designers know what is going on with the software they make, it is not easy to understand it.

It’s not just software development that requires documentation.

The documents to be written when it comes to algorithms are also very complicated.

It can be said that many computers and computer-derived industries involve various messy document majors.

Even product managers often have to write and output requirements documents and the like.

Otherwise, it would not be that easy to change the requirements.

Writing documents is very troublesome, and both programmers and product managers hate this stuff.

But it’s not enough if you don’t write documents.

Because in highly organized enterprises.

Not only do we make things, we also have to be good at presenting our ideas to others.

As for why Lin Hui didn't write these messy things before when he was working on software.

Largely because Lin Hui is the polished commander, Lin Hui does not need to show his thoughts to others.

In addition, this time and space does not require separate declaration when it comes to software copyright registration.

In this way, there is no need to fill in additional software development documents for the several software Lin Hui developed previously.

But Lin Hui is just a special case in this situation.

But when it comes to multi-person collaboration, the position is not high enough.

It's basically impossible to say goodbye to documentation.

He Siyuan may now just think that developing software is cool.

I never thought about how troublesome it would be to maintain software and various documents.

Lin Hui felt it was necessary to let He Siyuan know these things.

At the same time, Lin Hui silently set a small goal in his heart.

In the future, he will definitely get rid of some very cumbersome "classical" formulaic things in computers.

Even if it cannot be eliminated, we should try our best to change the fate of the industry to a certain extent through our own efforts.

Of course, these are things for the future.

Among the books he bought earlier, Lin Hui found the two books "Easy Software Development Documentation: Practical Chapter" and "Program Maintenance Practical Guide" with almost no effort.

Lin Hui couldn't find "Programmer's Guide to Rehabilitation of Cervical Spondylosis", probably because he didn't buy it before.

However, Lin Hui found a copy of "Programmer Hair Care Secrets"

I think the effect should be the same.

No, this one seems to be even more injurious and extremely insulting.

Although it always feels weird to mix these books with super classics such as "The Art of Computer Programming" and "Introduction to Algorithms".

But it doesn't matter. He Siyuan fell into the trap or avoided it after reading these books.

I only hope that he can understand computers and computer-related industries from all aspects and angles before making a choice.

Although He Siyuan was told to bring him there at noon, Lin Hui was afraid that there would be other things at noon.

I simply took these books directly to the coffee shop from before.

After a few words of explanation to the shopkeeper, Lin Hui left.

After having breakfast outside, Lin Hui returned to Mingpin International's villa.

After struggling for a while, Lin Hui was no longer sleepy.

This is fine, but confusing right and wrong can easily disrupt people's biological clocks.

Lin Hui started to work again.

Lin Hui checked the emails in his mailbox. Normally, this was what Lin Hui did before going to bed.

But Lin Hui didn't rest yesterday. Therefore, these tasks naturally accumulated in the backlog.