Professional Python, Clean Code and Debugging on kodkod | Intro Course

Clean Code A: Good Names, Small Functions and a Single Responsibility

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

Until now the goal was “make the code work”. From today, the goal is also to make it clear. We will learn:

Clean Code B: DRY, KISS, Separation of Concerns, Comments and Refactoring

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

DRY — Don’t Repeat Yourself.
KISS — Keep It Simple, Stupid.
Separation of Concerns — separating responsibilities between parts of the program.
Comments — when a comment helps and when it hurts.
Refactoring — improving the structure of the code without changing its behavior.

Why do we need this?

In the topic on the computer and the operating system we wrote project_check.py with four almost identical blocks. What happens when we need to check 20 more files? Or change the message from OK to ✓? You have to touch 20 places, and in one of them you will surely forget.

Debugging A: What a Bug Is, Kinds of Errors and Reading a Stack Trace

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

What a Bug is.
The three kinds of errors: Syntax Error, Runtime Error, Logical Error.
How to read a Stack Trace (Traceback), Python’s error message.
The most common errors, and what each one says.

Why do we need this?

Developers spend a huge part of their time finding and fixing bugs. The difference between a beginner and a professional is not that the professional has no bugs, but that they read the error message and know within seconds where to look. Beginners see a lot of red text and panic. By the end of the lesson, the red text will become a map.

Debugging B: The Debugging Process and the VS Code Debugger

Mon, 01 Jan 0001 00:00:00 +0000

What will we learn?

In the previous lesson we learned to read errors. Now we will learn to hunt bugs, including ones that have no error message: