Good programming practice

Question

I read Randall Hyde Write Excellent Code (Volume 2), and I found this:

[...] its not a good programming practice for creating monolithic applications, where all the source code appears in one source file (or is processed by one compilation) [...]

I was wondering why this is so bad?

---

Thanks to everyone for your answers, I really want to accept more of them, but I chose the most synthetic one, so anyone who reads this question will immediately find the necessary things.

Thanks guys;)

Answer 1

Because everything is so crowded.

If you have separate files for individual things, you can find and edit them much faster.

, , .

Answer 2

, , , , , - . , , , API. , , , .

, C. , , , , , "" "" . "" , .., "" , API. "", , "" , API. "" , , , API. - "" , SQL- , "" .

Answer 3

() .

Answer 4

, , .

, , , .

Answer 5

:

• -, . .
• . " " " ".
• , . ( ) .

Answer 6

, HTML CSS " ", , .css,.js .html : .

Answer 7

. . , . , .

, , , , .

, ( ), , ( ).

Answer 8

​​ : , . , , .

, , , -, COBOL FORTRAN . , .

- - . OO , , , .

Answer 9

. " -" , , . , ..

Answer 10

, - . .

Answer 11

, , . , , , . , DLL, . , , , .

Answer 12

, . , , .

, .

, 3000- . . , , .

Answer 13

I think that you have never worked in a large company with 6,000 lines of code in one file ... and every couple of thousand lines you see comments like /** Do not modify this block, it critical */, and you think that the error is, you come from this block. And your manager says: "Yes, look at this file, somewhere in it."

And the code breaks all those great OOP concepts, has dirty switches. And like fifty participants.

Lucky.