Home → 2003/09/03, 22h41

Blogging about blogging

If you look at my blogroll (the links on the left), you can notice that most sites discuss weblog-related stuff (this is true on September 3rd, but may not be true if you read this later.) It is a little bit as if you like photography so much that you end up taking pictures about how to use a camera. In the process, you forget to take pictures that really mean something to you.

Blogs tend to naturally organize themselves into circles of interest. When you get into a circle, you eventually end up identifying the leaders. Once you have found important leaders, you generally do not need to go further as the rest of the bunch (those like me) is generally referring to these leaders. Consequently, my blogroll lists some leaders in the weblogging community that blogs about blogs.

I am a Java expert. So I am now looking for weblog leaders in the Java development circle. I started at JavaBlogs and I found a potential leader (I cannot tell for sure since I am just peeking at this circle.) He is a funny guy, I must say. Rude, but funny. I especially liked the faked interviews. I will refer to him as the DiveIntoJava guy -- style wise.

Here is an excerpt from the faked interview with Marc Fleury:

BB: You've often advocated the powers of JBoss caching, can you tell us a bit more about it?

MF: Actually, JBoss caching is very clever and complex. We give you the fabled option D to compete with options A, B, and C. We allow for incredible amounts of tweaking of cache behaviour, we've even implemented some truly mind boggling paradigms that reflect real world needs. Performance is clearly an academic issue, in the real world, people simply like as many options as possible. JBoss is so clever that it allows you to tweak these options to your heart's content, yet we always ensure we come out last in any performance test, in order to maintain consistency. We realize that every single application server other than JBoss has superior caching configuration and performance, but what we lack in those areas, we make up for in tweakability and lack of documentation.