Ok, lets see what people think about this one...
Quote:
|
Originally Posted by randomperson
Remember... programming is about laziness! The only thing that really matters in the long run is whether the program actually does what its supposed to do...
|
Also.. lets put this limitation on it as well..
Quote:
|
Originally Posted by randomperson
Now wait... programs with hundreds of thousands of lines of code... thats quite different. You HAVE to have some organization otherwise that would be completely unmanageable. I'm deinfitely not talking about something like that... if the linux kernel had no structure to it then linux users would be in trouble...
However, for your own project that needs to get done, as long as it works that IS what matters. After it works, then you make it look pretty.
As for software engineering... obviously when you make code for your employer, your job depends on it being consistant with the companies coding standards and has to work with other peoples projects... but for small personal projects it isn't as necessary (unless you're perfectionist).
Theres a reason why programming traditionally has been called "hacking"...
|
Hacking in the sense of "putting it together quickly".
Now please note I am not advocating sloppy coding practices and not commenting... as a person who programs mostly in assembler I know the value of comments! Writing without a purpose is pointless! Writing without comments is especially useless! As far as coding practices go, everyone should have some kind of coding style they adhere to and stick to it.. otherwise you're going to get confused when you look back on it... and obviously if the project calls for something else, then use that style...
Sure... you could probably phrase "laziness" better, but im lazy....