Posted by: Peter Alvarez on    |    Category: Development    |    Comments: 0

Avoiding the ‘Awful Parts’ in Web Development

Javascript: The Good PartsA couple of weeks ago I finished reading “Javascript: The Good Parts” by Douglas Crockford. The book highlighted how javascript, while having some amazing features, has some absolutely awful features (such as its dependence on global variables, not providing block scope for variables, and so-called ‘falsy’ values, to name a few).

Crockford proposed that javascript becomes a much more¬† valuable programming language when only a subset, which he calls ‘the good parts’, is used. This implies that the additional features (‘the awful parts’) of the language only serve to make it worse, and don’t actually provide any value to the language. This same concept can be applied to web applications (or any product for that matter).

A good web app is not designed simply by assembling a long list of features to throw together.¬† Too many features could end up making the product harder to understand and use. In fact, the more features there are, the harder it is to get them to all interact in a comprehensive way. Users aren’t usually impressed by a product with a large set of features. They just want something that works.

Careful forethought and dialog must go on before deciding on the final specs for a system. With careful planning, your web app will be more likely to provide a service with excellent features that are easy to understand and use.

Leave a Comment