Refactoring Dead Code

### Link to the coursework

https://github.com/CodeYourFuture/Module-Structuring-and-Testing-Data/tree/main/Sprint-3/3-dead-code

### Learning Objectives

- [ ] Identify 'dead code' in an existing code base
- [ ] Demonstrate how we handle 'dead code' in our codebases

### Why are we doing this?

The presence of "dead code" can impact the efficiency and developer experience of a code repository. Learning to refactor code to be clean and efficient will help you be a better developer and future-proof your code.

### Maximum time in hours

1

### How to get help

Share your blockers in your class channel
https://curriculum.codeyourfuture.io/guides/getting-help/asking-questions/

### How to submit

1. In your fork of the coursework repo, checkout the main branch
2. Make a new branch from `main` called `coursework/sprint-3-dead-code`
3. Make regular small commits in this branch with clear messages.
4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

There are several directories in this repo. [Make a new branch](https://simpledev.io/lesson/create-branch-gh-desktop-1) for each issue in each sprint. Only change files in the `Sprint-3/3-dead-code` directory.

### Anything else?

_No response_