The value of throwing code away

We had a discussion at work about “throw away” code. One of our developers was very against developing any code that would be thrown away afterwards. He referred to this as a waste. In my view sometimes the biggest gain can be in developing code that is meant to be thrown away. It can be used to try things and, more importantly, learn things that can shape the code that is kept. This article sums it up much more eloquently than I can.

A lot of developers also like to refactor existing code. This usually involves the removal of code they deem can be improved. In some ways, the initial code could be viewed as a prototype and hence it is fine to throw away that code … and at some point the code they have written will also be thrown away.

Links

Prototypes Are Worthless, But Prototyping Is Essential

Related Posts

One Life

For the first time in ages we had a family night at the cinema to see the film “One Life”. It is unusual for my wife and I to agree on a film to watch, let alone the kids as well!


Read More

Are you considering time sensitivity?

Somethings in life are time sensitive and some are not. A business opportunity may be time sensitive in that it will only be a success when certain things are aligned or maybe new technologies are available.


Read More

Cultural fit versus contributor

When we recruit people we are obviously looking at their ability to perform the role on offer but we are also looking at how well they will work with the team.


Read More