There’s an extensive email-based interview of us over on Subvert.ca. There’s juicy bits about certain large companies trying to kill off one of our early projects, column fodder, and the approaches we’ve developed for taking on new clients and starting new development projects. Here’s an excerpt:
Many people we speak to find it unusual that we don’t actively prospect, solicit, or answer blind RFPs, etc
Honestly, we like it this way: when we get a referral or start a new project for a past customer, there’s already a relationship in place. The client already knows that they can trust us, and it cuts out the entire “dance” that we’d otherwise have to do to prove ourselves. There are other benefits too.
People only ask us to prepare a proposal when they are seriously considering a project. Plus, we rarely find ourselves as column fodder behind another incumbent company—we call it column fodder when you have no hope of winning a deal and your estimate is just filling in a cell on a spreadsheet for comparison purposes.
This level of trust also means that we can work more closely with our customers to develop requirements. They take our estimates and advice seriously. In the end it works out better for everyone involved.
Great blog post from Carl over at nGen Works about what’s he learned over the last six years running his business, in particular this list of goals, or statements of intent:
- Understand what we want personally and align company and individual goals as much as possible
- Discuss issues openly and honestly
- Admit mistakes and fix them
- Take the high road in grey areas
- Consistently recognize good stuff and hold people accountable for bad stuff
- Support each other through successes and failures
Item 1 is not something you often see out of a company, especially the larger sort. Items 2 and 3 are things that people always struggle with, and they are a nice reminder to me who runs a musical operation on the side. It’s always tempting to make unilateral decisions or to try and cover up mistakes, especially public ones, and doing so always comes back to haunt you.
Shouldn’t I be able to attach notes to an email, say in Gmail or any other mail client, for internal/personal use? Things to remember, to come back to later? Almost like Stickies, or the Task list? Obviously it would just be a local thing, for organization, but man, that would be handy. Especially in our support bucket.
Maybe that’s one of those things Outlook has always done that I was never privy to, but it strikes me as the kind of thing that’s been missing for a long time. I do remember a time when I had pieces of paper on a desk that I had to deal with, and I would often attach post-it notes to those pieces of paper, writing down reminders about what needed to be done.
Maybe a Firefox plugin like FireGPG to hack into the DOM of a Gmail inbox! Okay, back to work now.
Clay writes over on the Sunlight Labs blog:
Once you start editorializing data— well, you’ve lost both accountability and transparency as well as credibility.
Sunlight Labs is a pretty cool project, where their focus is taking all that data the government makes available and digging into it to find out what’s actually going on. And one of the problems they have with a lot of the government projects like Recovery.org is that while they espouse transparency, they don’t actually provide the raw data, they editorialize it and provide websites and displays that spin it to their advantage. When you look at it like that, it’s the opposite of transparency. In fact, if you want to set up your own data mining and digging, and you want FEC data, you’re probably better off getting it from Sunlight, who’ve already taken the time to build machine readable databases for you.
On a related note, there’s an upcoming set of presentations called BigAppsDevCamps, for those who want to use New York City municipal data in their apps. It’s probably of interest to many mobile developers, and I was planning on stopping by if I can. I think that might be an example of government being a good wholesaler, as opposed to a bad retailer. Although that depends on what they make available and how. I don’t like the notion of filing an RFP just to get access, when it’s public data.
We’re starting to get a lot of questions about SQLCipher from developers, ranging from getting the source code to build environment integration and linking. In order to better facilitate use of the library, encourage the growth of a developer community, and to hopefully avoid repeating the same answers too often, we’ve started the SQLCipher Users mailing list on Google Groups. You can sign up over here.
If you use SQLCipher in your project, you should subscribe to get news about updates (like integration of upstream changes from SQLite), changes, and new features. Traditionally we’ve fielded questions about SQLCipher from our support email account, but from now on we’d appreciate it if all requests for help with this software be posted to the mailing list.