things to do when you open a deal with a new framework/codebase

Whenever we encounter a new framework, we'll ask two kinds of questions:

Structure questions

• Where is the entry point?
• Where is configuration loaded?
• Where is the transport?
• Where is the pipeline?
• Where is the worker?
• Where is execution started?

These help us navigate the project.

Responsibility questions

For every important class, ask:

• Why does this class exist?
• Who creates it?
• Who owns it?
• Who calls it?
• Who destroys it?

For example, for PipelineWorker:

• Why does it exist?
• Who creates it?
• Who calls run() on it?
• Who cancels it?
• When does it die?

Those questions reveal the architecture far better than just reading code.