Skip to content

🔵 Workflow 2.4: Make a Technical Modification to the Project

Phase 4. Copy the example, experiment, make a technical modification, and observe the results.

WHY? A technical modification confirms that the project can be changed intentionally without breaking the existing workflow. Small, controlled changes provide practice with editing code, running checks, and verifying results. This phase connects project understanding to hands-on implementation.

Professional Practice

After gaining a basic understanding of the project, its goals, and its techniques, the next phase is to copy each example file to your own file. Start by modifying the opening information, then make a small change to the technical logic and observe the results.

Save your work after each useful change. Git maintains a history of project changes, making it safe to experiment. When something goes wrong, we can review Git history and return to a working version.

Steps

  1. Git pull before changes
  2. Make a technical modification
  3. Run the project code
  4. Git add-commit-push