Today's lesson focuses on one critical goal: staying sane in CS. Programming and computer science can be incredibly frustrating! Machines are highly-responsive but also highly-inhuman, and too much influence from them can be harmful.
We'll address both left and right brain sanity. To satisfy your logical and critical left hemisphere, we'll look into several of the common error messages that you'll experience in CS 124 and discuss how to fix them. And to nuture your creative and intuitive right hemisphere, we'll talk about how you stay human while learning to communicate with machines.
All programmers make mistakes. All of the time. But you learn two things with time. First, how to fix your mistakes quickly. And second, that you are never going to stop making mistakes, so you might as well get used to it!
Below we'll walk through the three common kinds of error messages you'll need to handle in CS 124:
ktlinterror messages, caused by incorrect code formatting
Based on our prior experience, you should expect to make a lot of these mistakes. In Spring 2020, around 500 CS 124 students together made:
So get ready to make your own contribution to that total this semester. But there are some stategies that you can use to handle errors. Let's go through each category one by one.
Before Kotlin executes your program it transforms it through a step called compilation. We'll discuss this in more detail in a later lesson. But certain types of errors can occur during this step.
You can divide them broadly into two categories:
Let's look at both of these scenarios and how to address the errors that result.
Just because the compiler doesn't find any problems doesn't mean that your code is correct! It can still cause an error when it is executed. Below we examine runtime errors and how to fix them:
A lot of the code that you write in this class will be tested to determine if it is correct. This is done by running your code—like a function, for example—with lots of different inputs. If we find a case where your code doesn't match up with the solution, we'll show you that failing input.
In the walkthrough that follows we'll try and explain a bit about how the testing process works and how to evaluate the output.
Learning how to spot and fix errors in your code can be hard! So this semester we've come up with a new way to give you more practice. Below is our first example of a debugging problem—or stumper. CS 124 is the only CS1 course that is providing you with this kind of debugging practice!
How do these work? We started with a bunch of solutions from previous semesters. Then we introduced a small error into each that causes it to fail our tests. Your job is to fix it without modifying more lines that we did to break it.
As you go, examine the solutions submitted by other students. You may see ways to improve them, or other ways of solving the problem that you hadn't considered.
These are super fun! Let's go through how to tackle on together. While the one below is just for practice, we will have these on future lessons for credit, and potentially on quizzes as well.
Hopefully by now you'll have noticed that writing correct code is hard. There are a lot of ways to make mistakes. So programmers are always on the lookout for ways to make their lives easier and attempt to avoid bugs before they happen.
One way to do this is to use another feature of Kotlin known as runtime checks. Let's look at how they work:
One important caveat:
assert statements are not always turned on when you code is run.
Typically they are enabled during development (when the programmers are running the code) and disabled in production (when actual users are running the code).
assert is enabled on all of our playgrounds and for all of our homework problems.
check always work, so they can be safely used both in
development and during production.
We'll have you start using these checker methods on homework problems soon!
Now let's look at a simple example where we might want to use
Hopefully the walkthroughs and the statistics we presented above help convince you of one thing: you're going to make mistakes. We have both good news and bad news about that:
All today today we'll be discussing frustration, failure, and sanity. Below we talk a bit about how we work through those feelings in our own lives, and how we try and maintain a positive relationship with technology.