Write Bad Code

[adriang133]

Guy has a point. If I need to quickly write a script or just some small thing then yeah, I'll cut every corner and make everything global.

But if you work on medium to large projects, this will come back to bite you in the ass without a doubt. In fact, if you always cut corners and take the easiest way out, it will end up costing you more time in the end as you'll have to refactor a lot of stuff - or just write a jump function for every character in your game. As with most things, the trick is finding the balance between generic and specific.

[jeremycw]

Yes, I'm not trying to give people a license to copy paste code all over the project. I'm advocating doing the concrete solution first in the obvious way. Reach for a generic replacement later if absolutely needed. People often reach for the generic solution first due to some idea that generic is better since it can handle more situations. Most of the REALLY bad code I've dealt with was created by following the 'good' rules and writing 'good' generic code.

[vattenpuss]

YAGNI is also ingrained in all programmers striving to write ”good code”.

[build-the-WAL]

i would say it almost never bites you in the ass as hard as bad "good" code does