I had originally though it was a repost of the many older articles from Backblaze until seeing a reference to Dec 31 2014. While not terribly ambiguous now, the ambiguity will only grow as the year marches on.
If someone from Backblaze happens to see this: you don't need to put it in your URL, but please date your post near the top or bottom of the text.
The evergreen no date thing is fine with me - provided the content itself is actually evergreen. That's the bit people seem to forget. Not dating content doesn't magically make it last forever. If the information is unlikely to expire then I don't need a date. If there is a chance that the information will go out of date, especially if the dated information will not be useful to the reader, then it should be dated.
If anybody thinks, readers will skip their article, if the date is too easy to find, why don't you sign the article with the authors name and then let the author decide, if a date has to be added. Like "joe - Nov. 1, 2014" or just "joe".
This article certainly needs a date.
An article without a date is about as trustworthy as a scribble on a bathroom stall.
Hit Refresh. Lo and behold - there is the date.
Now that's an agile organization. Thanks very much - I really appreciate the date on these posts as well.
I appreciate, in the end you have to do what gets you the most views, however, from my perspective missing out the date means you prefer to waste my time as I have to scan the article until I get a feel for how old it is.
I would read anything written within 6 months and would consider up to 12 months if the information was high quality. It's not like we're overburdened with quality, independent, information.
If your going to be business minded, why not have the date on for the first few months and remove it when the first flush of green has gone. ;-)
It's not a euphemism. It's a standard term in web content for articles that are not time-sensitive. An article on how Quicksort works is an evergreen article. One on predictions for tomorrow's stock market moves is not.
That said, yes, TLS 1.0, RC4, and SHA1 are all starting to smell, and it's probably time to toss them down the drain.
@Yev, writing about specific technology is time-bound and doesn't exactly have the half life of DNA.
Having said that, I appreciate all that Backblaze writes about hardware. It's interesting and easy to read. This takes time and thought, you (at Backblaze) must be doing something right.
If you don't date your articles, they're of casual interest only, because I can't be sure they're current enough to use them as the basis for decisions.
- Show last update date on all posts;
- The evergreen posts you just update every 3-6 months to keep them updated and still green;
- The not evergreen posts can be considered not useful therefore let them be old.