Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m reading Randall Hyde’s Write great code (volume 2) and I found this:
[…] it’s not good programming practice to create monolithic
applications, where all the source code appears in one source file (or is processed by a single compilation) […]
I was wondering, why is this so bad?
Thanks everyone for your answers, I really wish to accept more of them, but I’ve chosen the most synthetic, so that who reads this question finds immediately the essentials.
Thanks guys 😉
Because everything gets so crammed.
If you have separate files for separate things then you’ll be able to find and edit it much faster.
Also, if there’s an error, you can locate it more easily.