What we're creating with Krugle is a search engine for software developers. I.e., no more pawing through pages and pages of Google searches, hunting around various web sites, etc. trying to find useful results for technical information. We're crawling millions of technical pages and sucking down terabytes of source code using Nutch, processing pages with Antlr-based parsers, and serving up the search results using Lucene.

The site is currently in a limited beta and we're getting great feedback. I just saw that we're the most anticipated launch on the Museum of Modern Betas. Heck, that's even cooler than winning a DEMOGod award.

So, if you know any take-no-prisoners, hardcore people who want to work on a project that's actually making developers' lives better... Krugle is hiring.

Kevin Lawrence (and the Agitar crew) talk about the philosophical contention between the notions of For All and There Exists. That is, the difference in mindset of existentialists vs. universalists. Looking at debates in e.g., the extreme programming world, there's a lot of confusion and arguments back and forth that stem from this constructivist vs. deconstructivist conflict.

The biggest tragedy in these debates, IMHO, is that people on both sides of the fence polarize and calcify in their self-righteous positions. The fact is that we need some amount of both approaches to succeed. For example, writing test-first leads to horrible code if you don't also refactor as you go. Accretive unit tests that aren't themselves refactored leads to big, ugly and unmaintainable test suites. More simply, positivist (aka "garden path") tests must be balanced with deconstructivst (test (to) destruction) tests.

Stepping up a level or three, it's even better if, rather than merely mitigating and ameliorating problems, we change the game such that it's hard/impossible to even articulate bad ways and trivial/easy to articulate the garden paths. That is one of the biggest benefits to taking a linguistic approach to development.

Updates:

Note that folks using non-Gecko based browsers are not able to view or add comments about the draft on the web site but you can submit comments via email.

For those who can't read the draft easily on the official website, Tim Bray has put up an easy to read version that is suitable for printing.

Simon Phipps and Danese Cooper co-wrote their notes from the release presentation.