Maintenance code in the following two situations, you find that which makes you mad.

Maintenance code in the following two situations, you find that which makes you mad.
One is to know what the code is going to do, but the logic exists in more than one class, and with the mass use of event delegation and distribution, you need to see how the functionality is implemented.
The other is that while the code is in one piece, execution is also from top to bottom, but without annotations, you have to see what the code wants to achieve.

This issue has been closed because of a discussion-based question of non-technical questions

Reply content:

Maintenance code in the following two situations, you find that which makes you mad.
One is to know what the code is going to do, but the logic exists in more than one class, and with the mass use of event delegation and distribution, you need to see how the functionality is implemented.
The other is that while the code is in one piece, execution is also from top to bottom, but without annotations, you have to see what the code wants to achieve.

The first kind of nausea.

The second, if you can do the code, that's a comment. That's very comfortable.

