Kismet is a great tool for wireless survey and collection but many of the 802.11 tools out in the wild leave a lot to be desired. I often find myself wanting to create something very specific to fit my own needs. Luckily for us, programming with Kismet is not all that hard and frankly, Kismet is awesome so we don't have to reinvent the wheel here.

I wanted to take the opportunity to share a solution I had for one of my grievences with the existing Rails asset pipeline. For multiple reasons, I absolutely despise how all my JavaScript is compiled into a single file. This isn't a blog post to argue the merits of the existing strategy used by Rails but provide a simple alternative.

Disclosure, this is just a concept and not necessarily the most effective way of implementing your own before and after callbacks using Ruby.

Open and edit your last migration with a single command! If you hate opening migrations as much as I do then you will love this tip. Since migrations begin with a datetime group, create an easy to use bash function to quickly edit that migration.