Hello, and welcome to Evernote’s new technology blog. Our main company blog is a great place to learn what we do, and this is the place where we’ll talk about how we do it (and, occasionally, why…).
This will include tidbits about our various applications from Engineering, our service infrastructure from Operations, our API from the Developer team, and our advanced indexing/searching technology from R&D. Phil Constantinou (our VP of Products) and I (the CTO) will try to keep a variety of bits flowing here.
Why? Two reasons:
- We couldn’t have created Evernote without access to the wealth of information other people have provided as they tackled similar problems and posted their solutions. We want to return the favor in case that can help someone else.
- Transparency. We think that our users (and partners) have a right to know how Evernote is built so they can continue to make informed decisions about using us for their life’s memories.
These posts will be technical. Some may be painfully so. I’m talking “screen shots of emacs in hexl-mode” and “B-splines for curve fitting.” Our target audience is other developers, sysadmins, researchers, and technology entrepreneurs who might find something useful (or at least amusing) in our experiences.
That means this blog may not be intelligible or interesting for non-technical Evernote users. For less technical discussions, we’d recommend our main blog, our user forums, and Support if you’re having a technical problem with your own account or software.