I agree with most of what you say. But uncommented code isn't necessarily a bad thing. You can often make it self documenting through long and descriptive variables names and function names.
I just want to use a "message queue"(or what ever), the one I'm trying to use has the semantics I need for a project. I just want to use it, not learn to maintain it. I don't want to have to spend weeks reverse engineering the tests to figure out how to make it work, I just want to build with it.
But, how do I know which Queue system to use? does it have the right semantics? what happens when you fill the queue, does it pause the producer or emit an exception? who knows, just look at the code! (this makes selection of systems really hard, unless you have the sacred knowledge)
And thats the problem. Meta might have the world's best scaling primitives, but unless you can find the right person to ask, you'll never really be able to figure out _how_ to use it in your project in any reasonable timeframe
