ocd

@TheHydroImpulse 
Yeah playing around with the comments.

On one level it makes sense to not have any comments, because if you name your stuff well then it's pretty much all redundant. Same goes for JavaScript and CSS, no need to comment the constructor or the exports.

But if you look at it another way, it serves as visual cues. It focuses your attention. It's like the whitespace, it's mainly there to focus your attention. It's like repetition, I really feel like it helps your brain stay aware of where it's at and what's happening.

I have never in my life used CSS comments, but then I saw someone use them and it makes it feel so much simpler and easier to follow.

https://github.com/suitcss/utils-display/blob/master/display.css

```css
/**
 * Display-type utilities
 */

.u-inline {
  display: inline !important;
}
```

Then I have never seen anyone use shell comments before until TJ and jwerle:

```bash

#
# Log <msg>.
#

log() {
  echo "  ○ $@"
}
```

https://github.com/jwerle/suggest.sh

```bash

## output usage
usage () {
  echo "usage: suggest [-hV] <query>"
}
```

And C:

https://github.com/visionmedia/watch/blob/master/src/watch.c

```c

/*
 * Milliseconds string.
 */

int
milliseconds(const char *str) {
  int len = strlen(str);
  return 'm' == str[len-2] && 's' == str[len-1];
}
```

There's no reason to comment any of those really, but it just adds more context so it's easy to sustain attention or something like that. So the makefile is just like those.