This week we’re going to do as much of the homework as we can in the lab. That’ll give you some insight into how we think when we’re writing code, and how to break down the problem in a way that you can actually fix it.
This week’s folder has three exercise files. You should start at 1 and then do 2, and then… do 3!
When you make a test pass, make a git commit. This level of granularity will help you recover from mistakes in the future.
Code is complicated, and you need to be able to understand large amounts of it in small amounts of time! If it is formatted consistently, then you don’t need to use brain cycles to understand what’s going on.
Git tracks all changes, regardless of their importance. If everyone on the team obeys the linter’s rules then there should be very few diffs with low demantic value.
Exceptions should be made in the real world. If you want to line some things up to make their meaning clearer, then you should! However for these first few weeks, your work will be auto marked, so if it’s not 100% perfect according to the linter then it won’t pass that test.
Exercise 1 is all about linting. There is some code that is perfectly fine from python’s point of view, but remember: