HackerTrans
TopNewTrendsCommentsPastAskShowJobs

SickOfItAll

no profile record

comments

SickOfItAll
·vor 6 Monaten·discuss
First of all, nothing that any of us have to say today will have any value in 100 years. (And probably a lot less than that.)

Putting that inconvenient fact aside, there’s virtually no chance that a “website” you build today will work in 100 years, so you can’t think in terms of the digital representations we use now. The future might as well be populated by aliens. Instead think in terms of self-renewing systemic processes and incentives:

Create a trust that upon your death periodically (every 5 years?) doles out a pot of money to your descendant(s) who ensure that your writings are published on whatever form of Internet/“Web” exists at the time. Hire a law firm to enforce the terms and hunt down your descendant(s) at the appropriate times for a cut of the money. In theory, this could continue forever as long as the money grows and the amount remains incentivizing.

The other option since that will be expensive is to attach your writings to genealogical records on Ancestry, or register them with the Mormon church (who are major genealogical record keepers). There are many people who diligently steward those records down the years, and there is a fair chance that they will be rediscovered by someone in your line of succession. Having a lot of kids will help the cause—and your picaresque adventures in doing so would give you something to write about that people might actually want to read about in 100 years.

Or, you know, just print a book and give it to your kids as a family heirloom.
SickOfItAll
·vor 11 Monaten·discuss
It’s simple, but developers are generally terrible at it, especially the ones who are ‘smart’: Aim to think in terms of contracts and interfaces, not implementation. I don’t want to know what’s in your black box in order to understand how it works; if you make me read your code, you’ve done it wrong.
SickOfItAll
·vor 11 Monaten·discuss
Clearly the author wrote the article with multiple uses of "may" and then used find/replace to change to "might" without proofreading.