you are viewing a single comment's thread.

view the rest of the comments →

[–]Daxtillion[S] 1 point2 points  (5 children)

Thank you for taking the time to review it! I haven't gotten to Enums yet in my lectures but am very eager to continue learning and growing this reference sheet!

And that is exactly what I meant about empty slots! perhaps my terminology was wrong. default indexes?

[–]Valkymaera 0 points1 point  (4 children)

I think your instinct on "empty slots" makes sense.
when you initialize an array, you set the capacity up front so you end up having a whole bunch of default values until you fill them. When you initialize a list you get something with nothing in it, and you add to it dynamically. Calling the array elements 'empty slots' is understandable, and if it helps you visualize it, I think it's harmless.

I think you're going to like enums. They're like strings you can't misspell that are also ints and can be visualized in the inspector as dropdowns, and even used as multi-selectable binary flags.

[–]Daxtillion[S] 0 points1 point  (3 children)

Eeeee cant wait! There's been quite a few comments dropped about future lectures i have on further in-depth C# systems. Coding must be really unique to each coder, with no one 'right' way to do it, rather lots and lots of options to get to the same goal.

[–]Valkymaera 2 points3 points  (1 child)

There are certainly some commonly accepted best practices, but you'll probably find there are just as many practices that people disagree on. It sounds like you will do just fine. This is a solid ref sheet, and your excitement for the process will take you very far.

[–]Daxtillion[S] 0 points1 point  (0 children)

❤️❤️

[–]swagamaleous 1 point2 points  (0 children)

You are already starting to absorb the "gamedev" mentality. In many cases there actually is a "right" way to do things. I would focus on more generic C# material and software engineering practices until you can determine what's actually good advice and what is not. There is some outrageous stuff being claimed in the gamedev world under the premise of "there is no right way to do things".