why I project in modifying a 50000 lines of code, there is always a feeling, the change is to always feel afraid there correction,
Extract was forced myself from the original file, the new change
So,
Small projects can,
Why is this so? Am I perfect personal requirements?

CodePudding user response:

Must move slowly!

CodePudding user response:

Gai change point by the way,
All test, don't change the test again, don't know it stepped out the problem

CodePudding user response:

This is because not familiar with the project, not enough confidence, only afraid of trial and error

CodePudding user response:

This is sick, you want to, I'm not kidding, just like some people, go out, want to go home to confirm whether forget closed, is ill,

CodePudding user response:

SVN or other tools to change the part of the test no problem, submit and set the stage identification convenient (recovery)

CodePudding user response:

reference 4 floor arpnet99 response:

this is sick, you want to, I'm not kidding, just like some people, go out, want to go home to confirm whether forget closed, is a disease,

Well,,, I always think you forgot to close, in fact habit has pledged I closed, but I always cannot help to confirm again,
Obsessive-compulsive disorder???????

CodePudding user response:

CodePudding user response:

That's because you haven't read it yet

CodePudding user response:

The

reference 7 floor VisualEleven response:

No, I have read, I may be required too perfect, and especially worried about where the correction,
Is my lack of confidence?

CodePudding user response:

Line 50000, also want to split into different files, different directory, you can't say a source code file has 50000 rows, extract from the original file, the new change, means that you have been in the old, in a recession, have a tendency to elderly forgetful, need to have a rest

CodePudding user response:

I need to learn to use software: UltraCompare Professional or Beyond Compare

CodePudding user response:

CodePudding user response:

references to the tenth floor mlqxj35674 response:

50000 lines, also want to split into different files, different directory, you can't say a source code file has 50000 rows, extract from the original file, the new change, means that you have been in the old, in a recession, have a tendency to elderly forgetful, need to have a rest

A CPP has 50000 rows

CodePudding user response:

references to the tenth floor mlqxj35674 response:

50000 lines, also want to split into different files, different directory, you can't say a source code file has 50000 rows, extract from the original file, the new change, means that you have been in the old, in a recession, have a tendency to elderly forgetful, need to have a rest

Thank you for your reply, suddenly wake up, may I really old, tired

CodePudding user response:

The

reference 13 floor qq_30691863 reply:

Quote: reference to the tenth floor mlqxj35674 response:

Line 50000, also want to split into different files, different directory, you can't say a source code file has 50000 rows, extract from the original file, the new change, means that you have been in the old, in a recession, have a tendency to elderly forgetful, need to have a rest

A CPP has 50000 rows

A CPP has 50000 rows, worship...

CodePudding user response:

The

reference 13 floor qq_30691863 reply:

Quote: reference to the tenth floor mlqxj35674 response:

Line 50000, also want to split into different files, different directory, you can't say a source code file has 50000 rows, extract from the original file, the new change, means that you have been in the old, in a recession, have a tendency to elderly forgetful, need to have a rest

A CPP has 50000 rows

A CPP 50000 lines of code? You are in the international joke with me? This is what a shitty wrote it? Quick dismiss this silly force, this kind of person is not suitable for development

CodePudding user response:

Please keep in mind: the source code itself whether writing structured object-oriented or comply with the design patterns or agile... Is not important, the important thing is whether you using structured or object-oriented or comply with the design patterns or agile... Method named identifier, read, modify, inspection, test source code,

Mean you program structure seems more reasonable, more concise, does not necessarily than looked a mess when running or modify the program structure are less likely to make mistakes, more convenient to modify, wrong where is easier to find the cause of the error and the error, it is easier to correct mistakes,

Try comparing
Library (on the classification of the book is structured enough)
And
Any search engine (is considered to be a flat structure data, only support full-text retrieval)
Which to process information more convenient, more efficient,

So
Rather than strive to refactor your code make it looks more concise, more reasonable
Learn as laborious grep, sed, awk,... This kind of full-text search and batch editing tools,

The more complex structure, the harder it is to change, the more difficult it is to debug,
Sometimes (or even most of the time), seems more reasonable, more concise code, run up the worse performance, when something goes wrong, the more difficult it is to find reasons to find what went wrong after correction, the more difficult,

Programmers do not try to avoid mistakes, but focus on quickly discover and correct mistakes, really in a quick way to solve the mistake easily, "rapid failure" than "to prevent error", Fred, George

Before Microsoft c # editor's development director Jay Bazuzi listed some questions to help find the right direction; He felt that former colleagues should use these questions to ask yourself; Actually regardless of where is the work of developers should always ask yourself these questions:
In pieces to ensure this problem will not appear again, "what should I do?"
Pieces to a less "Bug, what should I do?"
Pieces "to ensure that the Bug is easy to be repaired, what should I do?"
In pieces "to keep on changing fast response, what should I do?"
In pieces "to ensure that my software running speed, what should I do?"
If most of the team can ask yourself from time to time, is bound to benefit from, because these are really powerful,

CodePudding user response:

I have never changed to, like mine, dig out, ruled out, but looking at the ray is an eyesore, find a place to bury the, clean up the world,
After a long time, has been stepped on, once again, mine engineering
In this way, your boss will continue with you, if,,, you are not far from the left,

CodePudding user response:

There is always puzzling problem, the change is the when found resolve not to drop the idea of change is produced from the original file,
1, remember, there is a problem not escape, otherwise you will encounter later
2, version control is necessary, SVN, soucetree or something, even if the code you write it again in reverse, version rollback can also easily get

CodePudding user response:

Oh my god, a CPP 50000 line, black question mark???????

CodePudding user response:

Completes the version management, rest assured bold to change!

CodePudding user response:

I've also is such, see now are directly change, bai, there is a problem to change rest assured bold try,

CodePudding user response:

Go out, want to go home to confirm whether the forget closed.
I went home so repeatedly confirmed a few times,,,,

CodePudding user response:

Baidu search "how to treat ocd!" "

CodePudding user response:

Estimation is you did not use a version control.
Version control, (such as git, SVN). Then we would like to how to change can change, don't worry about the problem of correction.

, of course, under normal circumstances, should be to modify a function, you need to do the relevant tests, make sure there are no more questions, submitted version. Then the next function. This is the right way of thinking. A function is wrong, can return to the code at any time. Don't worry about doing this.

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull