By Topic

Embracing Nihilism as a Software Development Philosophy and the Birth of the Big Book of Dead Code

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)

Agile software practitioners often brag about how quickly they can change course with a project as the requirements evolve and change. What happens to the things we no longer need? Are projects removing functionality no longer needed by the project? Are we truly willing to abandon or even (gasp! delete) "dead" code. Do we know dead code when we see it? Even the most agile developer has left unnecessary code because it "might" be used in the future. Even the most agile product manager has left a seemingly useless feature because "someone" might want it.

Published in:

Agile Conference (AGILE), 2012

Date of Conference:

13-17 Aug. 2012