#Yandere simulator code code
If you are in a team just follow the code style, the point isn't to make code pretty, but to make readable to many in the same group.Īlso I guess that worry comes from the stupid piling on yandere simulator code, which cause a lot of misinformation about programming to spread.
So at this point "switch" vs "if" is mostly an aesthetics concern, and that depend on the future of your code design too, switch is great if you have a single statement to test, and that in the future you won't need to break due to exception, it's a bit more verbose too. Also performance is only solved through profiling first and then addressing the actual necessary problem, you get to have the thing work first, THEN you make it performant after profiling, THEN you make it pretty for your ego OR to share with your team.
In fact, the process of programming mean that, as you discover the need of your project, you will need to "refactor" the code, ie to re write it to make better and leaner, so don't get block too early on issue like that, most code are actually ugly anyway, despite the cultural wars that happen in programming forums, most production code, ie on a schedule with deadline, will be "bad", it's very easy to find very high profile example from notable company. Hierarchy of memory access will be a bigger bottleneck, but at your level it's probably not even on the map, you probably wouldn't be pushing high level performance code that soon. Generally "if" is unlikely to slowdown your computer in any capacity, not on modern hardware, this isn't the game boy era anymore.
You don't know what you don't know, and practice (that mean failing and making mistake) will teach you better. As a fairly new programmer, your first concern should be to finish things and get shot down, everything else comes after.
0 kommentar(er)
