#Oh and the difference between Write and WriteLine makes sense and I'm happy

[quidcumque]

Humungous praise to Bob Tabor of "C# Fundamentals for Absolute Beginners" - he's teaching this like I taught Latin. Like you SHOULD teach a language, ie taking small chunks at a time, oversimplifying to introduce ideas (but letting you know it's oversimplified), LIBERAL EXAMPLES, and frequent review. I've wanted to learn coding for years, but I'd fizzle out in frustration after a self-study session or two because fuckers would list out every data type (with REMARKABLY insufficient explanation of the differences), then slam me with the linguistic equivalent of "if Aster has four apples and Frank has nine, what is the projected yield of a mature apple tree?"

Like fuck me okay so the int type stores whole numbers from -2,147,483,648 to 2,147,483,647 which is a whole fucking bunch of numbers but then the LONG type has uhhhhhhhhh a lot more commas in it and I can't even remember what the FIRST LESSON PRACTICE CHALLENGE was but I remember googling four different concepts and frowning a lot

Bob ain't doing that. He took two separate videos to 1) create your first C# program and then 2) UNDERSTAND your first C# program. By the time I finished the video after that, "Understanding Data Types and Variables", I only have two data types and the ability to read and write via console

BUT

Goddamn, I actually understand some shit now. No, I don't REALLY know why there's four different data types just for numbers, but it doesn't matter because he told me I don't need to worry about that shit right now. What I can grok though is that the Class Library is a giant building of books that I don't have to keep in my house. Those books have all the shit I'd have to do by hand if it wasn't stored in the book. If I type Console.WriteLine it's like saying "hey go to the Console book and get me the shit from the WriteLine chapter." I get that, and I like that. I technically know that the period between is called a "member accessor" but that's not useful to me yet so who cares

OH! AND! Variables are kinda like buckets, right? They hold stuff for you to get at later. Different buckets are better for holding different kinds of stuff (data types), and you gotta label them to find the right bucket again later. So you declare a variable to say you need such-and-such size bucket and you're going to call it such-and-such. Then you assign stuff to the variable-bucket. You can use that label later to retrieve that stuff, for whatever use.

But wait there's more. You got operators which help you work the info. I only know = and + right now, but they're pretty fuckin common sense at the moment. Which is great, because then I'll be comfy with the idea of them by the time we get to the weird ones. Naming conventions are pretty damn important, because 1) C# is case sensitive and 2) there's a fuckton of text and your eyes are going to bleed so do the things that help prevent eye bleed (like camelCasing your bucket names). Leading straight into the last point, which is that programs get stupid long, so Initialization squishes the Declaration/Assignment steps into one line. Fewer lines equals less eye bleed + less carpal tunnel, and we're all good with that

So, like, I don't fully know what methods are, or classes, or what tf static/void/args/etc are for, but I now ABSOLUTELY trust that I will learn them and I won't be mad at everything in the process.