I would consider that a negative. > There should be one-- and preferably only one --obvious way to do it. Whats going to happen when all professional code is

I would consider that a negative. > There should be one-- and preferably only one --obvious way to do it. Whats going to happen when all professional code is using `attr.attributes` but all the documentation uses `attr.s`? Anyway its a minor point. I personally think it is a poor decision when a programmer decides to be cute than clear.