We are working hard on RavenDB 3.0 and a lot of the work now goes into the spit & polish phase. Usually this is a pretty boring part. Making sure that intellisense works in the right places, that the UI makes sense, that we give the right results, that the logs are helpful, etc.
But occasionally we get to actually do really cool stuff in this phase, and one of them is this guy:
Map/Reduce is a very powerful technique, but it can be hard to figure out issues sometimes. We always had debug endpoints to help actually figuring this out, but we are now putting a lot of attention on surfacing them to the user and making this easy to understand.
The map/reduce visualizer is a great example of that.