Crossover: 2014

Chapter 167 Guide to Avoiding Pitfalls in the IT Industry
How to avoid pitfalls for a person who yearns for a job as a programmer?
Lin Hui felt that there was no need for any heavenly book with esoteric theoretical knowledge about computers.

There is no need for a textbook that is as vague as Tan Hq's book.

There is no need for purely preaching books on the meaning of life.

Only three mediocre books are enough to make most people who are originally interested in programming ape work unable to say.

The three books are: "Easy Handling of Software Development Documentation: Practical Combat", "Practical Guide to Program Maintenance", "Practical Rehabilitation Collection of Program Ape Cervical Spondylosis".

Of course, it doesn't have to be the same title.

Other books with similar and homogeneous content to these books also have good persuasion effects.

The reason why this kind of book is dismissed is not because the content of the book is deceptive.

On the contrary, these books are rich in content and very 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-mentioned books objectively reflect the three super troublesome things that a programmer faces in his career:

——Documentation, software maintenance, occupational diseases.

This is easy to understand about occupational diseases.

After all, programmers often have to face high-intensity computer work, and staying up late is even more commonplace.

These may not be very discouraging to a person who is interested in working as a programmer. After all, many occupations 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 found in 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 where the software runs, it is necessary to modify the software to adapt to these changes, which requires adaptive maintenance.

The needs of users are constantly changing. During the use of software, users will put forward new functional and performance requirements for the software. In order to meet these new requirements, the software will be modified to improve its functions and performance, which requires comprehensive maintenance. .

Using advanced software engineering methods to redesign, code and test the software that needs to be maintained or a certain part of the software to improve the maintainability and reliability of the software, etc., and lay the foundation for further software improvement in the future. This is called preventive maintenance.

There's a lot of messy maintenance on top of that...

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

And the work related to software maintenance is very troublesome.

When debugging, everyone is looking forward to standard comments.

When writing bugs, almost everyone forgets to comment.

Some big bastards who copy and paste also like to make it into a "black box" form, and then package it blindly.

There are a lot of troubles.

However, although this is troublesome, software maintenance is a technical matter anyway.

For technical matters, this is within the programmer's own job. Although such things are troublesome, they are obligatory.

The endless variety of documents that bothers programmers the most is one of them.

I am a program ape with a background in engineering/soft engineering as an undergraduate, and there are simply endless documents involved in work or study.

During his college life in his previous life, the biggest impression he had on Lin Hui when he was a sophomore and a junior was the endless experiment reports and all kinds of messy documents, which were very annoying.

(... I don't know what the situation of online classes is 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, it is necessary to write detailed design documents, unit test plan documents and integration test plan documents, etc.;
In the development stage, although there is no need to create new documents, it is also necessary to deal with the documents, and the programmer needs to modify the previous documents;
In the testing phase, unit test reports, integration test reports and system test reports should be written;
During the release phase of the software, it is necessary to write installation manuals, user manuals, upgrade guides, etc.

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

Uh, although many software designers know what's going on with the software they make, it's really not easy to explain clearly.

Documentation is not just about software development.

The documents to be written related to the algorithm are also very complicated.

It can be said that many computer and computer derivative industries involve various messy documentation professions.

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

Otherwise, it is not so easy to change the demand.

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

But the documentation is not enough.

Because in a highly organized enterprise.

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

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

Largely because Lin Hui is a polished commander, Lin Hui doesn't need to show his ideas to others.

In addition, this space-time involves software copyright registration without a separate declaration.

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

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.

Saying goodbye to documentation is basically impossible.

He Siyuan may now just look at developing software as cool.

I never thought about how troublesome it is when it comes to software maintenance and various documents.

Lin Hui felt that 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" stylized things in computers.

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

Of course, these are all things in the future.

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

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

However, Lin Hui found a copy of "Programming Ape Hair Care Cheats"

Presumably the effect should be the same.

No, this book seems to be more harmless and extremely insulting.

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

But it doesn't matter, He Siyuan can avoid the pit after reading these books.

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

Although He Siyuan told He Siyuan to take it there at noon, Lin Hui was afraid that there would be other delays at noon.

Simply take these books directly to the previous coffee shop.

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

(End of this chapter)