What you are used to is not the correct way

If you have not watched it already, go watch the Apple battery video here:

http://www.apple.com/macbookpro/

Prior to watching this video and understanding the reasons for an enclosed battery, it was difficult to understand Apple's decision.  Now, I am going to wait for the new enclosed battery to make its way to the 15" MacBook Pro before purchasing one.  It all just makes sense.

I think this is a great example of how we can get used to something, and think that it is the "correct" way.  But, in reality, the thing you got used to (and thought was the "correct" way) was created because of faulty design, laziness, or the lack of innovation.  

I see this phenomenon a lot in programming.  Some examples might be:

• Premature optimization
• Valuing computer processor time more than developer time
• Writing unreadable clever code because it is "faster"
• Stored procedures and triggers
• Not using an ORM

Posted via web from Structurally Sound Treehouse