I blog. Obviously! But I felt that an influential blogger like Hugh Hewitt might give a good overview and write a book worth reading. Boy, was I mistaken.
This book is squarely targeted at non-technical, right-wing, religious Americans who don’t mind being sneered at. Anybody else should try to avoid it.
For that Anybody else group, here is couple of reasons from the book itself (emphasis mine).
An audience test that really should have been on the book’s jacket and not on the page 88 of the book:
Lance Hankins got annoyed with having to eyeball ant’s output of the long classpaths and wrote a task to do the classpath output in a slightly more readable form.
Neat, but perhaps there is a more generic way to do it. After all, not only ant produces these long semi-column separated monstrosities.
So, I want to show how I do it with Vim (Why Vim…).
Let’s use Lance’s output as given.
C|Net News has an C|Net News has an talking about Legacy (mostly mainframe) skills and how they contrast to the skills developed in the modern world of Linux, Web, Java and .Net.
It is a typical high level article where each word is important, but the whole passage is hard to read.
On the other hand, we have [C|Net News has an C|Net News has an talking about Legacy (mostly mainframe) skills and how they contrast to the skills developed in the modern world of Linux, Web, Java and .
Alan Williamson is planning to present about Open Source application that most of people don’t know about.
He is also asking the community to contribute their lists. Well, I have three tools that I like enough to mention (again).
Ethereal Whenever you have to troubleshoot an application with a lot of network traffic, Ethereal is a good tool to keep in mind. It allows to see the network traffic on both high and low level and is flexible enough to narrow down exactly to the information subset needed.
Ok, so they don’t. But there are some bits they do hate and Rich Bowen goes through big issues present in apache’s configuration file. Warning, it is a PDF file.
What I find interesting is that we see the full circle feedback in action here. Because the people supporting apache are mostly the same people who are developing (or documenting) it, they have credibility and strength of getting things done. Sometimes, within days….