This is the 59th episode of the StackOverflow podcast where Joel and Jeff sit down with Damien Katz (of CouchDB) to discuss non-conventional databases, non-conventional programming languages, and taking on non-conventional programming projects.
Stop, do not pass go, do not collect $200: watch Damien Katz' outstanding Rubyfringe presentation, CouchDB and Me. It is a hugely inspirational presentation for any working programmer. I can't recommend it enough. Go watch it now!
We have forgiven Damien Katz for working on Lotus Notes. Mostly. To his credit, he did write some very cool code, as documented in his famous formula engine rewrite.
You can think of Damien Katz' CouchDB project as the distilled "good stuff" from Lotus Notes. Wait! Why are you running away? Come back! It's not that bad! We swear!
Damien used Erlang to build CouchDB, largely because it makes error recovery and multiprocessing so much easier. Or as Damien says "what happens when everything goes to s**t". In other words, networking fails, or you don't have enough memory to complete the operation. This is stuff that is very tricky in C++, but almost trivial in Erlang.
On Damien's journey as a software developer: "eventually you get tired of working on stuff for other people."
The negotiations with IBM included the synonyms "douchebags" and "vapid bureaucrats". They seemed to appreciate his honesty (at least for the set of bad eggs he's referring to), and Damien is a guy who has spent some time in the bowels of IBM and knows what he is getting into.
I liked that Damien, when he reached analysis paralysis in the middle of his project, turned to the soothing, calming midwestern voice of Steve McConnell -- and the classic (and my favorite) book Code Complete 2.
While building up two new 1U servers for superuser.com, powering on the server with the cover off would trigger the Moro reflex in our 3 month old baby... two rooms over! That's how loud they are. REALLY loud. I was happy to have UPS take those out of my house.
I didn't appreciate how much happier I would be with community moderation -- I am unburdened from being the judge, jury, and executioner of the occasional serious misbehavior. It's a group discussion now -- thanks to our awesome community moderators, we can reach a concensus together!
What does it mean for an open-source project to be version 1? Version 0.1? Version 0.5? When is it good enough to use? Should you look at commit activity; is the project alive? Or should you look at how many people are actually using the software, regardless of version number or commit activity?
If you're a developer, and wondering what specific problem CouchDB could solve for you, Damien says: "would the data you have typically be stored in a document in real life?" The classic example is a contacts database. Do you have a phobia of storing large blobs in a database?
I think most hardware-oriented software developers have gone through this thought process at least once: "Hmm. I have gobs and gobs of system memory. Do I really need a swapfile on disk any more?" Don't try to outsmart the operating system designers, unless you're an operating system designer. And that goes triple for programmers who think they are language designers!
We answered the following listener questions on this podcast:
- Maayan: "What is your stance about using open source software in production code, when the open source project in question is working, but is either below 1.0 or is not actively maintained?"
Our favorite Stack Overflow questions this week are:
Can I do transactions and locks in CouchDB? A brief discussion of how this works in CouchDB versus a typical SQL database.
Any benefit or detriment from removing a pagefile on an 8GB RAM machine? short answer: no. Long answer: no. Fantastic answer by user quux, who also has an excellent sysadmin blog that we recommend checking out.
If you'd like to submit a question to be answered in our next episode, record an audio file (90 seconds or less) and mail it to email@example.com. You can record a question using nothing but a telephone and a web browser. We also have a dedicated phone number you can call to leave audio questions at 646-826-3879.
The transcript wiki for this episode is available for public editing.