I generally operate from the position that code must have a reason to exist. If it doesn't have a reason to be there, or be at this particular place, then it should be deleted, and I don't think twice about deleting code. So I tell my team that every piece
> Stop the world, I want to write it all down! > -attributed to Donald Knuth [http://en.wikipedia.org/wiki/Donald_Knuth] Permanent Students In my opinion, a programmer can do his job in the most productive way by believing that he is always a student. There are always multiple paths
> I beseech you, [gentlemen], consider the possibility that you are mistaken [http://en.m.wikiquote.org/wiki/Oliver_Cromwell]. > -Oliver Cromwell I'd like to tell you a story. When I was first hired at my current job, I was given a task: build a search engine for our company intranet.
> "I don't understand the problem here. The interface is intuitive, it makes perfect sense! So why do they want to keep the old one?" A coworker said this to me during one of the lunch-and-learns I present every couple of months at my job. What he unwittingly did was reveal