I think the point of the post is that there's more to life than "frameworks". Not every problem is worth solving, and not every problem is an engineering problem.
As for some problems not being worth solving, sure. But that's a key facet of the engineering/lifehacking approach: don't prematurely optimize, and don't try and optimize anything until you've figured out how to measure your goal.
So unless you have an example of a problem where engineering strategies don't apply, I'm going to keep applying them.
Here's an example: When I was 18 I wanted to listen to some new music. This was when we got our music on CDs, and we didn't have algorithms like iTunes Genius to help us find something we might like. I bought something just because I liked the cover art. Fortunately I ended up liking the album. (It was this one: http://rateyourmusic.com/release/album/dink/dink/)