July 30, 2006

Vader Sessions


July 23, 2006

Another First

<database id="foo" doc_count="1010" last_update_seq="1010"/>

Minutes ago, this was the first bit of database information served from a CouchDb server to a web browser. Database "foo" was a test database left over from a unit test.

The Fabric engine is fully hooked in and soon the REST api will be functional. I am very close to producing an alpha release of the project. The first release will be private with just a few testers. If you are interested in getting a look and giving some feedback, send me an email: damien_katz@yahoo.com


July 21, 2006


Brendon Upson recently open sourced his Java application server, Puakma. "Puakma"? What an odd name eh?

Well, now he explains the true origin of the name. It's not the name of a legendary Maori chief like he said for years on his website. No, it's much better than that.

Hint: It's an acronym, the first letter is for "Pucker".


July 18, 2006

"stupid users are putting important data into spreadsheets"

Oh, those stupid lazy users, if only they'd learn to put their data into normal form and enjoy all the benefits of a relational database.

BitWorking - Document Centric


July 17, 2006

Something's Missing

secretGeek - Web 2.0: Something's Missing


July 13, 2006

Volunteer wanted

I'm just a few weeks from a public alpha release of CouchDb. As such, I like to actually create a proper project website, but I don't have the time to do it myself right now.

I already have the domains, but I'd like someone to create the site with all the stuff a project site should have, and maybe also keep it running. Nothing too fancy is needed, but this is certainly a fair amount of work.

If you are interested in being the CouchDb project webmaster let me know.

Thanks everyone who offered to help. The project Webmaster will be William Beh. I think we'll have a new site ready in just few weeks. More later...


July 5, 2006

Making Reliable Distributed Systems in the Presence of Software Errors

How can we program systems which behave in a reasonable manner in the presence of software errors? This is the central question that I hope to answer in this thesis. Large systems will probably always be delivered containing a number of errors in the software, nevertheless such systems are expected to behave in a reasonable manner.

Making Reliable Distributed Systems in the Presence of Software Errors

I've only skimmed this, but it looks to be a great introduction to the Erlang development philosophy. I wished I'd found this a couple of years ago.

On a related note I am still working on the promised Erlang vs. Java articles, but I've been in an intense a coding mindset lately so the verbal part of my brain isn't very active right now. Maybe that's just an excuse for being lazy about writing. Anyway, I worked on it some during a beach trip this week, so I'm still making progress on it.


The Turing Tar-Pit

In programming, everything we do is a special case of something more general--and often we know it too quickly. -Alan J. Perlis

Raganwald: Beware of the Turing Tar-Pit

Interesting articles on Raganwald keep finding their way into my RSS reader. Subscribed.