Skip to content

Minor copy edits to dead code workshop #1679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
illicitonion wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Minor copy edits to dead code workshop #1679

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions common-content/en/module/js3/dead-code/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,9 @@ It means products we build can be maintained in the future without wasting more

As a programme evolves there might be many changes, fixes, feature additions made to the code. There is a high probability that when those changes were made to the code, there was no time to "clean" up the existing or old code. This can lead to **code being left in the repository that no longer has purpose**, whether by accident or on purpose.

One common way to identify dead code in our programmes is by using a {{< tooltip title="IDE" >}}A Integrated Development Environment, like VSCode.{{< /tooltip >}}. An IDE can often make unusable or unused code obvious to us through it's colour scheme.
One common way to identify dead code in our programmes is by using a {{< tooltip title="IDE" >}}A Integrated Development Environment, like VSCode. IDEs are special kinds of text editors which understand programming languages. This means they can add extra functionality, like syntax highlighting, and refactoring support.{{< /tooltip >}}. An IDE can often make unusable or unused code obvious to us through its colour scheme.

When we remove dead code we can reduce the "bloat" of our code, making it easier to maintain and improving debugging processes.
When we remove dead code we can reduce the "bloat" of our code, making it easier to maintain and improving debugging processes. It means we don't need to read and understand code that isn't used.

{{<note type="exercise" title="Exercise">}}
📖 Read this more detailed breakdown of dead code from Devopedia: https://devopedia.org/dead-code.
Expand Down
Loading