My browsing habits for the past 2 months. Pages per day is a crude metric, but good enough to get an idea of how many I look at per day.

I wrote a little script that scrapes ~/Library/Safari/History.plist and throws the the page title and url into a 150 line rails app which spits out basic info and lets me search through to try and find pages I remember but otherwise would have a hard time getting at.

The sqlite3 database is at 2MB after 2 months, I don’t think that 1MB/month is an unreasonable size to keep track of the pages I’ve been too. It might start getting unreasonable a few years from now, but nothing that can’t be handled then.
I don’t know why I wanted to have all the pages I go to logged into a system, even just for private use. Something about leaving a trail, having instant recall. I probably read more stuff on the internet than I do out of books, and I could remember for the most part what books I read, but there’s no way I could keep track of the thousands of webpages I go to every week.
It also just puts things in scale, I mean holy shit. In the past 7 days I’ve been to ~2300 pages. Not all different pages. In the whole 2 month period this thing’s been going, I’ve been to ~1900 different sites (judging by top level domain). That’s a lot of browsing.
The big idea that I feel is behind all this: when I’m 40 I’ll be able to come back and sit down and take a look at all the data I’ve left behind. Maybe figure out what my life had been like at some point in time. What websites did I visit 20 years ago today? Where did my interests lay, what kind of stuff did I like? It might end up being a dry, boring as hell legacy; but there’s potential for it to be interesting as well.
So there isn’t anything harder to take then a subtle bug with little apparent cause. That’s why this sort of thing kills me:
/usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/errors.rb:94:in `check': cannot rollback - no transaction is active (SQLite3::SQLException)
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/resultset.rb:76:in `check'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/resultset.rb:68:in `commence'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/resultset.rb:61:in `initialize'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/statement.rb:158:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:211:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:186:in `prepare'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:210:in `execute'
from /usr/local/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.1.0/lib/sqlite3/database.rb:620:in `rollback'
... 13 levels...
from /usr/local/lib/ruby/1.8/test/unit/autorunner.rb:200:in `run'
from /usr/local/lib/ruby/1.8/test/unit/autorunner.rb:13:in `run'
from /usr/local/lib/ruby/1.8/test/unit.rb:285
from test/unit/workout_test.rb:10
There are time when I’ll just get fed up with the damn computer, and this caused me to wrap up last night and go try to learn to read music1. There was even less information in that error as there is in musical notation! I can almost deal with sound visually on a staff, but it’s real troubling to deal with a bug that won’t leave the slightest clue.
But I think I’ve got it scrubbed out. Commenting things out strategically leads me to not want fixtures with nil values. Changing this:
invalid_exercise:
id: 4
name:
description:
into this:
invalid_exercise:
id: 4
name: ""
description: ""
mopped things up real well for me. Now there’s just one more thing that is making me want to bash my laptop with a rock, as soon as I can find it, I’ll be for smooth sailing.
1 Quite the feat actually: I quit piano in 6th grade because although I could play whatever anyone threw at me by ear, no way did I have the patience to learn to read those goddamned notes.
So I’ve got a rails app up that is handling bigger datasets then I’d imagined it would. It’s not doing so well and now I need to go through and optimize things. Ugh. But check this out:
[kjell@ambrose:~/Sites/quizzer] % cat production.log | wc -l
1541890
That’s a 1.5 million line logfile. Again, Ugh. At least people are using and mostly liking my system. Too bad it looks like it’s ridiculously inefficient. But ah, the joy of computers. Just think about that – it comes close to blowing your mind.
12:38 < xal> sam-: 2 things
12:38 < xal> a) you are nuts. those selectors are pure crack
12:38 < xal> b) could you add them to actionpack so that update_javascripts grabs them?
13:02 < madrobby> c) add more crack
1.0 really doesn’t mean much, I’m running on edge rails and have all kinds of cool stuff that wasn’t included (rjs, anyone?). But it’s great none the less.
Ruby has just started its ascend. Sure, it’s a rocket take-off, but we haven’t even left the atmosphere yet. DHH
This presentation from David is spectacular.
I'm sure I'm not the only one to have figured this out, but is this cool or what?
:complete => { visual_effect(:BlindDown, dom_to_update, :duration => 1),
visual_effect(:highlight, dom_to_update, :duration => 1) }
Rails hits c|net, buzz buzz wow.
I’m doing a questionnaire app with rails for the psych department at Morris, and this will kick ass when it comes to implementing questions on a scale.
So I’ve been working a campus job since school started, and it’s starting to suck. 10 hours a week tethered to a computer in an office. Windows! I’ve been lucky to have previously worked with rails, because so far php is to viciously scratching yourself as rails is to a warm oil massage. It might just be the spaghetti code, maybe it’s the syntax, or maybe specific to the legacy cms that I’m using, I don’t like it.
Excellent look at how rails and rapid development will change the software world. Homesteaders vs. Gold Diggers is a nice allusion, I don’t know which I’d rather be.
Curt Hibbs quickly glosses over why rails is so good, worth a read.
Ruby is really starting to hit the big time. I picked a good one to start with. I’m working with php now with my campus job, and it really pales in comparison. Now ruby leapfrogs both perl and python into a prestigious publication.
More rails hotness, this time a personal finances app from Jamis Buck. I like it.
Good bit of code for your functional tests that ensures your markup is valid.
PragDave is going after mainstreaming ruby. He doesn’t demand anyone use it – he leaves other languages their cut – but hasn’t said a bad word about ruby yet.
Plus he redesigned his site and now it looks exactly like one I’m working on now. His titles are darker blue, and there’s a little triangle on the left, but otherwise the same.
Not universally, but it’s sure a great option to have.
What is a huge deal? Having an extremely
I’ve wanted to build (exactly) this for awhile now, but I don’t have a gps, so what’s the point.
Dave Thomas, et al.
I’m a little late catching the bandwagon, but I didn’t buy the (beta)book for a few weeks after it’s release. This is a spectacularly detailed book on the rails framework, capturing the simplicity of setting up a rails application in it’s tutorial followed by quite a dense summary of the different aspects of rails quite in depth.
Cute way to generate cached image files from your db with rails.
Rails kicks butt.
In much the same way that the web took off because of “View Source”, Rails is taking off because it lowers the barrier to entry and holds nothing back.
Having learned html and css by viewing the source, I can say that rails works much the same. I love open source, and it makes doing things for a kid with little programming experience like myself a piece of cake.
Looks nice.
And I’m excited to see the numerous projects, but their site is down! At least they stayed up the 24 hours.
Now, on to Rails. Rails is the most well thought-out web development framework I’ve ever used. And that’s in a decade of doing web applications for a living. I’ve built my own frameworks, helped develop the Servlet API, and have created more than a few web servers from scratch. Nobody has done it like this before.
So rails, starting to get hot, huh?
I want to do railsday, but don’t know if I’ll be able to make the time on saturday. Hm…. I’ve got some killer ideas, but not too much rails-fu. But I could probably work out something in a day, rails is pretty easy.
Why we like rails:
Ruby on Rails is turning out to be that place in the middle capable of igniting excitement from both ends of the spectrum.
So what we’re basically trying to achieve is the meeting of quick’n’dirty with slow-but-clean into quick’n’clean.
when rails works she is like a sports car covered in hot babes. mrpotatohead (irc)
Could you say it any better?
A nice rails/ajax howto. Using, of course, the rails goodness that is Hieraki (man thats hard to spell). Here’s some more on rails and ajax, and also a demo of what dave has going on.
Interesting perspective on why ruby isn’t for new programmers – but it’s for me just because I don’t want to deal with C right now, and it’s real nice and quick.
Such a cool addition. I wish everything was as cool as rails.