Time Travel: 2014

As for processing multiple news summaries at the same time?

This is a bit unrealistic, and it involves the limitations of the algorithm.

In fact, whether it is the first generation text summary algorithm or the second and third generation summary algorithms.

When it comes to news/text summary processing, it is actually implemented one by one individually.

Mainly because although text summarization is simple, it actually takes up quite a lot of resources.

To achieve true parallel processing, at least we have to wait until the fourth generation of summary algorithms comes out.

The dependence of the fourth generation summary algorithm on the model will be greatly reduced.

However, it is basically impossible in this short time.

Now even some programs that rely on large servers claim to be able to process multiple texts at the same time.

But the actual processing is also done one by one.

Even if the user makes multiple inputs, the server will still process the first news/text first.

The first input news has been processed, but it still shows that it is being processed. The server actually starts processing the second one...

And so on, until the summary processing of the last input news is completed, and then the summary results are output together.

It may seem to the user that multiple outputs are achieved after multiple inputs.

But this kind of "multitasking" is actually just a cover-up.

Although this approach is not difficult to implement.

But Lin Hui didn't want to deceive himself.

I browsed the comment area below the Nanfeng APP for a while.

Lin Hui found that many users in the comment area strongly suggested that Lin Hui use Nanfeng APP based on

Create a professional mode that is more in line with the usage habits of professionals.

It doesn’t matter if you pay extra for it.

Many comments reflect this appeal.

Ah, Lin Hui has always been someone who pays great attention to user feedback.

It’s hard not to meet the reasonable requirements of users!

Lin Hui summarized the demands for professional mode from users who asked for an update in the comments.

Lin Hui was surprised to find that these people's demands were similar to the suggestions of the guy in the comment area just now.

They all require the lifting of the 10,000-word input limit.

However, there are great differences among these people on whether to handle this function with multiple news items.

It's outrageous to actually start a fight in the comment area.

Lin Hui took a look at the different viewpoints of the two parties.

Proponents argue that the ability to multitask increases productivity;

Opponents believe that multitasking can easily lead to distraction and affect concentration at work.

Well, as expected of a dedicated journalist, the support and opposition are entirely based on work efficiency.

Lin Hui wished that these people were debating whether or not to have multi-tasking.

In this way, he can openly maintain the status quo of this controversial point.

There is no need to make a fuss about multi-tasking. Even if you want to engage in professional mode, Lin Hui's workload is much less.

Just cancel the input limit of 10,000 words.

This is not a difficult task for Lin Hui, it is just a matter of changing a line of code.

Of course, even if you just change the code, you will still be charged.

It's not difficult to change a line of code, the hard part is knowing which line to change.

The normal routine for a programmer is a cup of tea and a pack of cigarettes, and one line of code can be modified in a day.

Not to mention that one line of code can be modified in a day. Sometimes it is common for more than ten people to modify three or four lines of code for a month.

It's not that programmers are passive and slow in their work. The problem is that it is really difficult to debug the same code written by others.

The pointer is placed randomly even if you don't play well.

There are no notes or anything.

The situation without notes is better. I am most afraid of encountering the kind of Mars notes that are comparable to the ghost paintings of old Chinese medicine practitioners.

It's really just one person's remarks and ten people guessing.

Why not ask the person who wrote the code?

Laughing to death, I have resigned a long time ago.

The most important thing is that when changing the code, you not only have to endure a mountain of the same code.

We also have to face constraints caused unintentionally by our peers.

Lin Hui can't say that in other industries, but the programmer industry is not suitable for large numbers of people.

At least not completely applicable to the situation where there is strength in numbers.

There is no linear relationship between manpower and time.

A large number of people cannot shorten the software development schedule.

Instead of helping software production, a swarm approach creates trouble and produces worse software.

Adding manpower to a project that is behind schedule will only make it fall further behind.

Because new personnel need time to understand the entire project, additional communication consumption is added.

When there are N people who must communicate among this group of people (no class relationship), when N increases, its output M will offset its benefits or even go backwards.

In fact, the concept that manpower can be exchanged for time is extremely wrong.

In other industries, it may be 1+1\u003e\u003e2

However, the strange phenomenon of 1+1\u003c0 is likely to occur in the computer industry.

The most direct inspiration from this incident is about the construction of future teams.

About forming a team? Definitely have to build a team.

but not now.

A team is not Lego. It can be put together as soon as you put it together.

Teams need division of labor and cooperation between members.

Cooperation requires tacit understanding.

Not everyone can be called a partner/mate

Although it may be a bit heartbreaking, it is true. In short, blindly forming a team is an extremely bad thing.

In fact, Lin Hui was very happy to be able to complete the early prototype of the team before the start of college.

…

Speaking of the professional model of developing Nanfeng APP.

After all, he was making changes in a code that Lin Hui was relatively familiar with.

It's relatively easy.

Lin Hui quickly found the key line of code.

When issues like overflow are not involved.

You don’t even need to change an entire line of code, just a number.

Yes, it's that easy.

In fact, this is also the reason why many people choose to become programmers.

I have to say, this feeling of manipulating everything through numerical values ​​is really cool.

However, it is this feeling of refreshment that makes it easy for people to lose themselves.

And jobs that are easy for people to get lost are more or less risky, even if the job is just a technical job.

In Lin Hui's previous life, several bosses with promising development prospects went astray because of the dark side of human nature.

Thinking about it makes people feel sad.

With such a lesson learned.

Lin Hui has always been walking on thin ice in an abyss.

Although he knew that he had the power to change the world at this time, he never dared to be complacent.

Steady development is the last word.

But this does not mean that you have always been stubborn. The computer industry is the industry that respects genius the most.

When you grow to a height that everyone needs to look up to, as long as everything you do is reasonable and can withstand scrutiny.

Even if you poke a hole in the sky, you will only gain tolerance.

After changing the code, some corresponding professional mode interaction issues will also be involved.

But these are small scenes.

Without much effort, Lin Hui mastered the professional mode of the software.