Timestamp Pet Peeve

June 24, 2008 @ 01:26 AM | posted by carmelyne

(last updated: 06.24.08)

Those timestamps are crucial.


If everyone started a good habit of correctly timestamping their blog post and placing timestamps where it's quite obvious like above or below the article header, then you could save a person about 3-4 hours per day of searching for the right resource. Timestamps like created_at and updated_at would be really extremely helpful.

Don't you hate finding an article where you're left to figure out if the blog post was written in 1995 and only works for version xx.xx of so and so App or Framework or OS.

Everyone appreciates a well timestamped article/post/story.

[ Last updated: June 24, 2008 @ 01:27 AM ]

Filed in Thoughts


1 Response to...
“Timestamp Pet Peeve”

  1. Michael Teter:

    Me too! I've ranted about this many times. It's always so discouraging to spend a few minutes searching for info, "finding" it, then, partway through reading it, you realize... this is from 2005!?

    In the tech world, anything beyond 18 months is stale.

    One good possibility is this new Google timeline feature (experimental). Here's an example: http://www.google.com/views?q=ruby+switch+view%3Atimeline&vwdr=2007+-+2007&btnmeta%3Dsearch%3Drestrict=Set+filter&num=5



    Posted: July 1st, 2008 at 11:58 AM

Sorry, comments are closed for this article.

Snippets of 06/24/07

Rails 'A'..'Z' Paginate

1
2
3
4
5
6
7
8
9
10
11

# Starts with 'A'..'Z' Paginate / model
def self.sort(sort)
  if sort
    find(:all, :conditions => ['name LIKE ?', "#{sort}%"])
  else
    find(:all, :order => 'name')
  end  
end

# index action / controller
@models = Model.sort(params[:sort])

Recent Posts...

RailsConf 2006
I heart devChix