April 28, 2013 1 Comment
Often when engaged in the construction of some piece of software, be it a web application or a native computer game, we get the Feature Fever. Our brains are trained by years of computer use to judge software by its polish. The tendency is misguided at best, and we try to think past it when fairly evaluating a prototype. But the fact of the matter is that even one or two polished aspects of a website makes it look better.
THIS IS A TRAP!
When you imbed a YouTube video or add rounded corners to your buttons, you are deceiving yourself. When you look at the screen, your eye is drawn to these familiar, visually impressive elements. Consequently, you subconsciously ignore or undervalue the unfinished parts of your project.
This leads to two things. First, you think you are farther along than you are. But more importantly, it makes you hungry for more features. Since one or two polished aspects look good, why not add more? Now you are on the hunt for short-term fixes that give big rewards in terms of visual polish, rather than working on the code that actually makes your program work.
If you start polishing before your core functionality is complete, you can get pigeonholed. When an interface element is polished, or some other unique feature looks amazing, you reflexively want to protect it. Even if the rational decision is to get rid of it and integrate the functionality somewhere else, you will keep the feature there. Letting form overpower function is a deadly trap.
The easiest way to add a polished feature is to search on the internet for code trinkets. Code trinkets are little snippets or blocks of code that you stick into your programs. Code trinkets are encapsulated, so all you have to do is paste and reload. Suddenly a beautiful new feature is completely finished.
Unfortunately, code trinkets have two downsides: they restrict your feature to exactly what is written, and they don’t leave you any smarter. Unless you take the time to figure out what ever line of the trinket does, and would be able to write it yourself (at which point it stops being a trinket), don’t use it!