Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
97 changes: 0 additions & 97 deletions 08_text_editors/1_setup.md

This file was deleted.

File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
5 changes: 3 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,10 +92,11 @@ Week 04 _(~2.5 hours)_

- Assignment #1

Week 05 _(~2 hours)_
Week 05 _(~2.5 hours)_

- Git strategies
- Assessing code quality: reviews and structures
- Debugging

Week 06 _(~2.5 hours)_

Expand All @@ -113,7 +114,7 @@ Week 09 _(~2.5 hours)_

- Object-oriented programming

Week 10 _(~3.5 hours)_
Week 10 _(~3.0 hours)_

- Text editors
- Assignment #4
Expand Down
6 changes: 6 additions & 0 deletions assignments/assignment_2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,3 +74,9 @@ By understanding we mean a very simple task: prepare a brief general description

1. Can you identify the main folders? Without looking at the code (you can only look inside other folders) what is their purpose?
2. Where is the main script of the package located?

# Assignment 2: code exploration using a debugger

The last part of this assignment is easy, but very important. One of the most common scenarios is to stumble upon code you have not written yourself. Especially when facing big projects, this might come across as a daunting task. Fortunately, debuggers come to the rescue! One of the possible use cases for debuggers is understanding a new piece of code, especially for studying its intricacies and connections. By introducing strategic breakpoints, one can understand the intended flow of the project and the different parts it is composed of.

That situation takes us to our next exercise: in the next module, we will focus on testing. But first, we would like you to use a debugger to try to understand how the current testing code actually works, what is being called, etc.