We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

What is the actual life expectancy of your code?

Formal Metadata

Title
What is the actual life expectancy of your code?
Title of Series
Number of Parts
96
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
As developers, our toolset for maintaining and improving our code spans from automated testing to build servers, refactoring tools, automated deployments etc. All these support systems are meant to improve the life expectancy of your code. In this session we'll ask ourselves the following questions: Is the life expectancy of our code actually improving or is this just something we like to tell ourselves to sleep better at night? When is it appropriate to call time of death on our code? Maybe when it's legacy? But what is legacy code? Three hundred developers have answered these questions in a survey that will be presented in this session. Let their answers be an eyeopener as to how you treat your code.