Shortest Path Academy

myButton.addEventListener('click', () => {
  messageDisplay.textContent = 'Button clicked!';
  setTimeout(() => {
    messageDisplay.textContent = 'Timeout!';
	myFunction(3, 4 * (5 + 2));
  }, 3000);
})

myButton.addEventListener( "click",
	function()
	{
		messageDisplay.textContent = "Button clicked!";
		setTimeout(
			function()
			{
				messageDisplay.textContent = "Timeout!";
				myFunction( 3, 4 * ( 5 + 2 ) );
			}, 3000 );
	}
);

myButton.addEventListener(
	"click",
	function()
	{
		messageDisplay.textContent = "Button clicked!";
		setTimeout(
			function()
			{
				messageDisplay.textContent = "complete!";
				myFunction( 3, 4 * ( 5 + 2 ) );
			},
			3000
		);
	}
);

As a side note, you see that in JavaScript I use double quotes instead of single. I do this because double quotes are used in other languages like C, C++, Java, and C#. I'm constantly switching between JavaScript and C++ or Java, so it's easiest for me to stick with double quotes.

Another side note: you see that I use additional spaces in expressions like myFunction( 3, 4 * ( 5 + 2 ) ). This makes the expression more readable to me than when everything is more crammed together.

• I think there's enough to learn, and enough anxious shopping, without throwing in the question of which web framework a beginner should learn.
• If I covered one or two web frameworks, it would add a lot of bulk to the course, and they might not even be the frameworks a given employer cares about.
• Web frameworks are more useful for larger websites and teams of programmers. They are less important for small websites with just one programmer, and in my experience, most websites are indeed small and written by one programmer. You probably do need an HTTP library to make a website, but you don't necessarily need a framework.
• Frameworks do a bunch of stuff for you, and they let you make a default website with "just a few lines of code." But I don't think doing that is especially enlightening. When you've done it "by hand" yourself, you can understand what the framework is doing for you, and that's more valuable.
• There are lots of good tutorials out there for each framework. When you want or need to learn one, you can.

The problem is that writing those tests is very time-consuming, and when it comes to user-interface code (the look and positioning of windows, buttons, animations, and so on) it can be very hard to do. It can also be hard to write tests for larger units, large parts of your program as whole, which often requires you to write "mock" or "harness" versions of the other parts, so that the part being tested can operate as if those other parts existed, whereas in fact they are fake versions, present only to set up certain test scenarios.

On the other hand, it is easy to write unit tests for individual functions or groups of functions that compute values. For instance, if you write a function that is supposed to convert a time from AM/PM format to 24-hour format, it is easy to write tests to confirm that the input "3:30 PM" gives the output "15:00", and that special cases like converting "midnight" to "00:00" also work.

There are examples of that function-input-output style of unit testing in this course.