Search results

shut up

WHJERE DIT MY OTHER 32 GJO

here is a delicate balance between well designed, easy to maintain, and efficient code. Softcoding is not always the way to achieve this balance. So please, just think about the systems you're designing and whether or not anything is actually improved. tl;dr elitism through "better practice" /...

to load information and whatnot. This is not good. Don't sacrifice code legibility and efficiency simply because they believe it makes coding experience easier. T

ecially true of smaller games made by newer developers. We shouldn't avoid adding certain QOL features simply because in a "properly" coded game it isn't necessary. This second point doesn't apply specifically to this conversation but I see it coming up frequently so here goes: a lot of people...

y'all need to stop with this softcoding stuff: You're generally referring to removing repeated code – and yes, this a good thing, normally. However, there are two issues with the attitude around this. First, not every situation mandates this kind of code structure. This is esp