Published by ugo on December 6, 2005
in web.
Darren Rowse: “While my “research” is far from scientific or accurate it’s an interesting figure. The average blog reader spends looks at less than two pages per visit.”
My statistics, as exemplified by the graph shown below (thanks to Google Analytics) are remarkably similar to those computed by Darren. I’ve tried to increase this ratio by linking to older articles in most entries here and this worked, to a point. Now I know that this is typical of most blogs: they just aren’t “sticky”.
If you have a blog, what is the average number of pages per visit that you see?
Published by ugo on December 6, 2005
in web.
Alex King: “Remember in the early days of the web when newspapers wouldn’t put their content online? Same thing here… eventually enough quality content will be in full content feeds and the partial feed folks will have to play along or they will become irrelevant.”
Hell, yes! I was trying to put my finger on the real motive why I dislike partial feeds, and Alex’s post pretty much nailed it. There’s so much content in RSS/Atom nowadays that I’m spending far more time in my aggregator than in my web browser (excluding the time I spend developing web apps). If you publish a partial feed, you are forcing me to first look at a snippet in the aggregator and then open the browser (or a new browser tab in NetNewsWire, which is not that much different). This makes my news reading much slower and, in the end, it sucks.
The RSS web is going to be as relevant as the HTML web. For us early adopters, it already is more relevant. Get over it and start providing full feeds.
Practical Subversion, by Garrett Rooney, Apress
I picked up this book because, after having worked for a long time with CVS as my only source control system, I moved to Subversion and needed to acquire a deeper knowledge of it (Incidentally, you would be crazy to still use CVS now that Subversion is stable and freely available). And deep does this volume go indeed. It’s written largely from the perspective of a repository administrator or a power user wanting to extend the system and develop new applications on top of it, as the long (73 pages) chapter on Subversion APIs demonstrates.
But even if you are a developer wanting to know more about Subversion because your company or favorite Open Source project just standardized on it, you’re bound to find a good deal of useful information in it. Just don’t think to be able to understand everything is you’re totally inexperienced when it comes to source control systems. In this case, I’d suggest “Pragmatic Version Control Using Subversion” as a more accessible alternative.
The introductory chapter (A Crash Course in Subversion) and the Best Practices chapter are very good even for beginners, anyway.
The writing style is clean and linear. Typography is good, apart from the horrible font used for the headings and the table of contents.
In conclusion, I don’t think you can find anything better, either online or in print, if you really want to make the most out of Subversion, so I give it five stars. The fact that it is not an introductory text should not detract from this judgment but, as always, caveat emptor.
