I say we answer them.

I use Vagrant for testing my config management and other automation tooling all the time.

I use it to provide a prod-like environment on which the dev teams can test their code so I don't have to hear "it works on my machine".

I use it to evaluate new tools without having to install it on the shared-infrastructure (which - depending on your environment - may incur additional work or cost).

I use it to run services that I may want to have around, but don't necessarily want running all the time, and may not want on shared infrastructure (short lived or seldom-used webserver or database instances, for example.)

If you don't want to answer them, then dont. If you don't want to see them, add a filter.

I say we answer them.

I use Vagrant for testing my config management and other automation tooling all the time.

I use it to provide a prod-like environment on which the dev teams can test their code so I don't have to hear "it works on my machine".

I use it to evaluate new tools without having to install it on the shared-infrastructure (which - depending on your environment - may incur additional work or cost).

I use it to run services that I may want to have around, but don't necessarily want running all the time, and may not want on shared infrastructure (short lived or seldom-used webserver or database instances, for example.)

If you don't want to answer them, then dont. If you don't want to see them, add a filter.

By default, filtered tags are greyed out. If you don't want to see them at all...