Programming Basics - Revision history

Zhell at 10:56, 22 March 2023

2023-03-22T10:56:40Z

Zhell at 10:45, 22 March 2023

2023-03-22T10:45:09Z

Zhell at 10:44, 22 March 2023

2023-03-22T10:44:38Z

Zhell at 10:41, 22 March 2023

2023-03-22T10:41:25Z

Zhell at 10:38, 22 March 2023

2023-03-22T10:38:37Z

Zhell at 10:38, 22 March 2023

2023-03-22T10:38:12Z

Zhell at 10:36, 22 March 2023

2023-03-22T10:36:08Z

Zhell at 10:35, 22 March 2023

2023-03-22T10:35:54Z

Zhell at 10:35, 22 March 2023

2023-03-22T10:35:35Z

Zhell at 10:34, 22 March 2023

2023-03-22T10:34:19Z

← Older revision		Revision as of 10:56, 22 March 2023
Line 1:		Line 1:
		+	[[Category:Tutorials]]
	If you’re new to programming, I’ll quickly introduce some of the vocabulary. Don’t worry if it doesn’t sink in immediately. The jargon will seem dense at first. But over time, you’ll pick up more. The best way to learn is by doing. So, with each time you play around with it, the programming terms will make more sense.		If you’re new to programming, I’ll quickly introduce some of the vocabulary. Don’t worry if it doesn’t sink in immediately. The jargon will seem dense at first. But over time, you’ll pick up more. The best way to learn is by doing. So, with each time you play around with it, the programming terms will make more sense.

@@ Line 10: / Line 10: @@
 To differentiate between the two:
-*Class definitions use a capital first letter, Car
+*Class definitions use a capital first letter, <span style="color: rgb(224, 62, 45);" >Car</span>
-*Instances use a lowercase first letter, car
+*Instances use a lowercase first letter, <span style="color: rgb(224, 62, 45);" >car</span>
 The '''class definition''', on the left, is what all cars share. The '''instance''', on the right, is a person’s car.

@@ Line 10: / Line 10: @@
 To differentiate between the two:
-*Class definitions use a capital first letter, <code>Car</code>
+*Class definitions use a capital first letter, Car
-*Instances use a lowercase first letter, <code>car</code>
+*Instances use a lowercase first letter, car
 The '''class definition''', on the left, is what all cars share. The '''instance''', on the right, is a person’s car.

@@ Line 10: / Line 10: @@
 To differentiate between the two:
-*Class definitions use a capital first letter, Car
+*Class definitions use a capital first letter, <code>Car</code>
-*Instances use a lowercase first letter, car
+*Instances use a lowercase first letter, <code>car</code>
 The '''class definition''', on the left, is what all cars share. The '''instance''', on the right, is a person’s car.
@@ Line 23: / Line 23: @@
-The common thing is that instances use a lowercase first letter. If you want to have a second or third word in the instance name, capitalize the first letter of each of the following words. That is called, camel case: heresAnEntireSentenceWrittenInCamelCase.
+The common thing is that instances use a lowercase first letter. If you want to have a second or third word in the instance name, capitalize the first letter of each of the following words. That is called, camel case: <code>heresAnEntireSentenceWrittenInCamelCase</code>.
 The instance name isn’t recorded by the car itself; the instance name is just how you refer to it in code. If you want the car to remember its name and to be able to ask the computer to tell you the car’s name, you’re going to have to set a property on the car. But first, let’s back up and think about, what really is a car, anyway?
@@ Line 30: / Line 30: @@
 Cars have attributes and actions. An attribute would be the car’s color. And an action would be like when you tell the car to drive. Here’s a quick explanation for both:
-*For an attribute, like color, developers refer to that as a property. You set properties with an assignment: car.color = "red". Then, you check on the value of a property: car.color … and the computer responds: "red".
+*For an attribute, like color, developers refer to that as a property. You set properties with an assignment: <code>car.color = "red"</code>. Then, you check on the value of a property: <code>car.color</code> … and the computer responds: <code>"red"</code>.
-*For an action, like drive(howFast), programmers refer to that as a method. You call a method: car.drive(55). The thing inside the parentheses, (in here), is referred to as a parameter. You use a parameter to pass something into the method. Methods can also have multiple parameters: playMusic(song, volume). In that method, you’re passing in settings to adjust the stereo system.
+*For an action, like <code>drive(howFast)</code>, programmers refer to that as a method. You call a method: <code>car.drive(55)</code>. The thing inside the parentheses, <code>(in here)</code>, is referred to as a parameter. You use a parameter to pass something into the method. Methods can also have multiple parameters: <code>playMusic(song, volume)</code>. In that method, you’re passing in settings to adjust the stereo system.
 == Creating a car ==
-When you want to manufacture a car, you call the ''initializer'', alternatively known as the constructor: new Car(). The initializer is a method, so it can accept parameters:
+When you want to manufacture a car, you call the ''initializer'', alternatively known as the constructor: <code>new Car()</code>. The initializer is a method, so it can accept parameters:
 <syntaxhighlight lang="javascript">
@@ Line 50: / Line 50: @@
 Here’s what’s happening:
-#You annotate your code with comments using two forward slashes, //. Then the rest of that line following the comment won’t affect your code. Class definitions are preceded by the keyword, class, and they use a capital first letter. You enclose the code inside both classes and methods with curly braces, { }. Inside a class or method, you indent the lines to make the code easier to read so that people can differentiate what belongs inside.
+#You annotate your code with comments using two forward slashes, <code>//</code>. Then the rest of that line following the comment won’t affect your code. Class definitions are preceded by the keyword, <code>class</code>, and they use a capital first letter. You enclose the code inside both classes and methods with curly braces, <code>{ }</code>. Inside a class or method, you indent the lines to make the code easier to read so that people can differentiate what belongs inside.
-#The initializer for Car accepts one parameter, color. You’ll call an initializer like this: const car = new Car("blue"). With that, you’re the owner of a shiny blue car and you can talk tell your friends about, “my blue car”. The const keyword is short for constant reference to a value. It means that the instance, car, will always be the same object. While you cannot reassign it to a different object, you can still change its properties.
+#The initializer for <code>Car</code> accepts one parameter, <code>color</code>. You’ll call an initializer like this: <code>const car = new Car("blue")</code>. With that, you’re the owner of a shiny blue car and you can talk tell your friends about, “my blue car”. The <code>const</code> keyword is short for constant reference to a value. It means that the instance, <code>car</code>, will always be the same object. While you cannot reassign it to a different object, you can still change its properties.
-#The keyword, this, is a reference to the object itself. So the initializer takes the color that you pass in and then sets the color property on the object. The property on the left side of the equals sign is what you are assigning the value on the right side: property = value.
+#The keyword, <code>this</code>, is a reference to the object itself. So the initializer takes the <code>color</code> that you pass in and then sets the <code>color</code> property on the object. The property on the left side of the equals sign is what you are assigning the value on the right side: <code>property = value</code>.
 == Where to go from here ==

@@ Line 1: / Line 1: @@
 If you’re new to programming, I’ll quickly introduce some of the vocabulary. Don’t worry if it doesn’t sink in immediately. The jargon will seem dense at first. But over time, you’ll pick up more. The best way to learn is by doing. So, with each time you play around with it, the programming terms will make more sense.
-== classes and instances ==
+== Classes and instances ==
 Programmers talk about the blueprint or general idea of a car as the class definition. Then many instances can exist, driving around in the world.
@@ Line 27: / Line 27: @@
 The instance name isn’t recorded by the car itself; the instance name is just how you refer to it in code. If you want the car to remember its name and to be able to ask the computer to tell you the car’s name, you’re going to have to set a property on the car. But first, let’s back up and think about, what really is a car, anyway?
-== attributes and actions ==
+== Attributes and actions ==
 Cars have attributes and actions. An attribute would be the car’s color. And an action would be like when you tell the car to drive. Here’s a quick explanation for both:
@@ Line 33: / Line 33: @@
 *For an action, like drive(howFast), programmers refer to that as a method. You call a method: car.drive(55). The thing inside the parentheses, (in here), is referred to as a parameter. You use a parameter to pass something into the method. Methods can also have multiple parameters: playMusic(song, volume). In that method, you’re passing in settings to adjust the stereo system.
-== creating a car ==
+== Creating a car ==
 When you want to manufacture a car, you call the ''initializer'', alternatively known as the constructor: new Car(). The initializer is a method, so it can accept parameters: