Usually, I would agree, except in this case the title gives absolutely no indication as to the topic of the article. Putting the word metaprogramming somewhere in the title would have been better.

Well, I could say "I'm sick of this metaproggraming shit." But I'm not sick of the metaprogramming, I'm sick of the conflicts. Or there's "I'm sick of the conflicts between other people's metaproggraming shit." That's closer to it, but doesn't capture my disappointment in the lack of progress in writing better tools. So there's "I'm sick of the lack of really cool metaproggraming shit" which is actually what bothers me and has the informal profanity I was going for.

So... Please feel free to fork my repo and retitle it I'm sick of the lack of really cool metaprogramming shit with my blessing.

The blog post title is fine, it's the post on HN that could use a little context. I think that's the point of this thread, anyway.

"Metaprogramming headaches: we've solved this before"

How about "I'm sick of Ruby's mediocre support for metaprogramming in-the-large"?

I'm sick of this shit (on the state of the art in Metaprogramming)