It seems that naming has been an issue that has plagued my entire career. Confusing names. Names that sound similar but mean very different things. I'm even guilty of causing it!
But if you take one thing away from this blog post: Couchbase is not CouchDB. They are both database products, with some common roots, but they are not the same thing.
Interested in learning more? Check out:
While I'm at it, let me clear up a few other naming confusions that have plagued me for a long time:
Working at OSU
Well, that's it. I started this post just to help and clear up the "CouchDB" and "Couchbase" thing, but it turned into more of a personal rant. Anyway. Couchbase.
I've just wrapped up my first week at Couchbase. So far, I like the job quite a bit.
One of the things I've been tasked with is to brainstorm a plan of things that Couchbase can do to reach out to developers, but specifically to Microsoft-oriented developers.
I've already talked to some of you for ideas, and I've created a huge list. The next step will be to pare down the list, prioritize it, and start working on it. But before I do that, let me send out one more appeal to developers of all kinds, including MS developers: what can I do to better communicate with and help you and your peers? Be as specific or general as you'd like!
One of the things that I've always liked to have on my blogs over the years is a "latest comments" widget. I like to leave all my blog posts open for comment indefinitely, and this gives users a way to see the latest comments, even if they are on very old blog posts.
The terminoloy that Disqus uses was a little confusing for me, but by reading some of the docs and trying a few tests in Fiddler, I was able to see that the forums/listPosts API endpoint was the one I wanted. You'll need to make sure that you have a public key generated in order to use the endpoint. Here's the widget I wrote:
Short version: My new job title is Developer Advocate, and I am working for Couchbase.
Long version: Being a developer advocate / developer evangelist is something that I've been considering for a long time. I've enjoyed speaking, blogging, writing, screencasting, teaching, helping, networking for a while now. But until now, I had always done these things only in my spare time. The thought of making those activities into my full time job appealed to me. But, there are a lot of developer advocate positions out there, and most of them don't appeal to me, because the product or the company doesn't appeal to me. The few times I managed to get interviews with really awesome companies with great products, it didn't work out, and I thought that maybe it wasn't meant to be.
But I'm very excited to announce that I finally found a DA opening with a great company with a cool product (a NoSQL database company based in Silicon Valley!).
I've done a lot of thinking this year about my career, and what direction I want to go. I've been a coder for my entire career. Some of the best parts of being a coder is sharing knowledge with other coders: teaching, writing, and expanding my own knowledge in the process. As much as I enjoyed working for my previous employer, they make a product that isn't developer-facing, and therefore a developer advocate position just wasn't going to happen for me there.
I'm ready to begin a new chapter, and I'm looking forward to reaching out to developers and helping to build the Couchbase community.
But there are two things that I would potentially lose that I was concerned about:
If I were migrating from WordPress or some other well-known blog software, it would have been really easy. WordPress->export, Disqus->import.
However, this site runs on my own home-grown blog engine (for better or for worse). I could have just left my legacy comments alone, and let them exist side-by-side on older blog posts. I called that "plan B".
But once I knew that I could import from other engines, well, I assumed there must be a way for me to "fake" it. It was a little bit of work, and it still might not be perfect, but it worked.
I researched the formats that Disqus can handle. One of them is the WordPress WXR format, which is based on RSS, which is based on XML. So, all I had to do was figure out how to generate the right XML. There isn't really a "spec" on the WXR, at least not one that I could find. Luckily, Disqus publishes specs for their own Custom XML Import Format, which is a version of WXR. Once I had that, it was a piece of cake to create an "Export to WXR" button on this very site. Here's roughly what it looks like in an MVC Razor View:
To import, I just saved the output of this view, and went to Disqus Import, and uploaded the file. It goes into a processing queue, and the time it takes with vary depending on how many comments you are importing and (I assume) how many other workloads that Disqus is trying to process. I imported 86 comments multiple times, and it generally took about 5 minutes at most.
Matthew D. Groves lives in Central Ohio. He works remotely, loves to code, and is a Microsoft MVP.