Tamizh in words

Don't leave the dead code behind

Published on
Read Time
· 1 min read

In software product development, we often remove or update a feature. This practice is widespread in early-stage companies to determine the product's market fit or positioning.

While removing/updating the feature, we often neglect the corresponding source code that powered it!

These source codes lie around with references to them all over the place. With the initial set of people leaving and new people joining, no one knows what this code does over the period. This, in turn, affects future code cleanup or refactoring, which is crucial for keeping the code clean and tidy.

If we don't keep the code in good shape, it will become a mess over time. It results in more development time for adding even a minor feature and many bugs.

How to fix it?

  1. Write code that is easier to delete
  2. While removing/updating a feature, prioritize the efforts to delete the corresponding code.

Do delete the unused code before they become zombies

Have you had any bad experiences because of the dead code? Leave a comment. I am looking forward to learning from you!

Like, Share or Discuss on LinkedIn , Twitter

Did the content capture your interest? Stay in the loop by subscribing to the RSS feed and staying informed!