after going through it with @torkelo, these things can be better about dev stack:
easy way to delete old raintank images, so you can just rebuild all images to make sure they are up to date (without wiping "base" images such as ubuntu etc that we're confident haven't really changed)
compilation of nsq tools is assumed. this should be automated
do we need the default raintank_code behavior where it just pulls in everything from master, potentially duplicating repositories you may already have in your gopath, and expecting users to symlink their code into raintank_code if they want to use their own code? maybe it's easier to just always refer to what's in your gopath, always reusing what's already there, or checking out new stuff if you don't have it yet. the latter approach seems simpler.
@torkelo anything else you think should be improved?
after going through it with @torkelo, these things can be better about dev stack:
@torkelo anything else you think should be improved?