2 ms·
Shouldn't the judge of evergreen-ness be from the reader, and not the author? If it really is timeless, people will come back and link to it again and again.
by iamwil 17y ago
Shouldn't the judge of evergreen-ness be from the reader, and not the author? If it really is timeless, people will come back and link to it again and again. I see the Norvig posts on learning to program in 10 years come up again and again here.
It sounds like if you wrote books instead of blog posts, you'd rip the covers off so readers can't judge it by its cover.
- patio11 17y agoWhy rip covers off when I can instead obsessively A/B test them and remove elements that hurt the business value of the IP I spent so much work creating, like dates? Here's the fundamental difference between me-as-employee and me-as-businessman: I will get paid for my labor of January 19th on February 30th, and will never see another penny of it even if what I do today has lasting value. What I do after I get home, though, I get paid for every year if it has lasting value. I will not cheat myself out of that lasting value by setting an auto-expires header on it.
- iamwil 17y agoI've had the same frustration as the OP where the date wasn't included when I was looking for time-sensitive information. It was a disservice to me-as-reader, and I ended up not reading the article and looking elsewhere, since I couldn't be sure of its timeliness. If that article was timeless, it's because I hear about it again and again from other readers linking to it, not because there was no date on it. Of course, I don't know what you write, nor have I seen the results of your a/b testing. So shrug.