Here's an idea for you: A service that you have to check in to periodically, you set up a number of actions that need to be done after you haven't checked in for 24 hours, 48 hours, 1 week, 1 month, 1 year and 5 years.
We'll call the thing 'deadmansknob', after the button in the locomotives that a train driver has to keep pressed to activate the system (if they have a heart attack they presumably let go).
Payment is on the signing up end (since obviously you won't be paying on the other end), $1 per action on file per year.
Your invention sounds like the perfect kind of thing to submit to the Halfbakery: http://www.halfbakery.com/
The difference between "this should be a blog post" and "this seems like something for people to use to amuse themselves with over lunch," I think, is that the blog-post kind of idea requires very little investment in time and labor to determine profitability. The kinds of things you see on the Halfbakery (and your idea) usually require large HR-investments, with employees either manufacturing the product, or directly serving the customer (or making sure that all the stuff you want to happen after your "death" actually happens.) You can't just sit down at your terminal and see if it's a great idea by morning, so it just becomes "something nice to think about" rather than "something nice to try out."
Interesting writing should contain both statements of fact and opinions. Having the writer provide cues to indicate which is which makes reading easier.
Otherwise, how does one quickly distinguish between an unsupported statement of fact vs. an opinion?
> If I have ten brilliant ideas, the best thing to do is to execute full-steam on one, instead of dividing my attention.
And this is the altered version:
> If I have (what I consider to be) ten brilliant ideas, the best thing for me, personally, to do, is to execute full-steam on one, instead of dividing my attention.
Now, there are things—aesthetic descriptors, like "brilliant" and "best"—that are completely subjective (except in certain jargon contexts, like "best-case efficiency.") Using an aesthetic descriptor is inherently implying that whatever you are saying is an opinion, because aesthetic descriptors have no other use—there is no way to "support" the "fact" that something is best, or most moral, or is the most dance-able, or tastes most nostalgic. These evaluations come from your utility function, not your model of the world.
All I did, here, was to add qualifiers to my aesthetic descriptors marking them as such. Frequently, I do the same to, say, a summary of a post by Zed Shaw, as a comment to that post, and people reply with "well why didn't he just say that?" It's bizarre to me, because these things are completely clear and never the subject of argument in spoken conversation—yet they seem to be points of ire almost always when online. I wonder if there's some sort of body-language cue that people normally rely on so subconsciously that they never realize they've avoided actually parsing any aesthetic qualifiers they've encountered, instead just inferring their meanings from analysis of tone and intent.
Now that I see what you were referring to, I fully agree with you.