oskarkv

I recently watched Rich Hickey's excellent talk Simple Made Easy http://www.infoq.com/presentations/Simple-Made-Easy/. After watching it I have noticed that a lot of tips I've heard and problems I've encountered boils down to what Rich was talking about; complecting.

For example this http://unlikekinds.com/post/17192015158 blog post argues that, when programming games, one shouldn't use inheritance for game objects. While a good piece of advice, using inheritance in this case is just a special case of complecting things.

But I've also noticed, and Rich mentions, that complexity (in the sense Rich was talking about) can be hard to spot. The more common the practice, the harder to spot. One example Rich brought up is positional arguments, or using lists to store certain kinds of data. For example: Storing a person's telephone number and name in a list [phone-number, name] complects the two. First, one has to remember the order. Second, if one needs to store, say, the person's address too, one needs to make changes to all the code that relies on the list's structure. A map {:phone-number the-number, :name the-name} does not have those problems.

I want to become more aware of, and sensitive to, complexity. HN, do you have any interesting or enlightening examples of complecting? Examples of complecting that a lot of programmers are blind to, like positional arguments, are especially welcome.