On February 21, we launched the first ever MongoDB Bug Hunt. We have been impressed with the community’s enthusiasm during the first week and have decided to extend the hunt until March 8. This will allow more members of the community to get involved and help improve MongoDB for users worldwide.
As a reminder, you can download the latest release at www.MongoDB.org/downloads. If you find a bug, submit the issue to Jira (Core Server project) by March 8 at 12:00AM GMT. Bug reports will be judged on three criteria: user impact, severity and prevalence.
We will review all bugs submitted against 2.6.0-rc0. Winners will be announced on the MongoDB blog and user forum by March 13. There will be one first place winner, one second place winner and at least two honorable mentions.
For more info on the Bug Hunt see our announcement on the MongoDB Blog.
Thanks to everyone who has downloaded and tested the server so far. Keep on hunting!
Dear CIO: Here's What Your Budget Isn't Telling You
The CIO is asked to do a lot: keep the network humming; secure the business from the Syrian Electronic Army; wrangle with gnarly vendors. But one demand stands above them all: cut costs. Most CIOs look in the obvious places -- replacing mainframes with commodity hardware; finding workloads they can migrate to the cloud; virtualizing and consolidating. Many CIOs evaluate where they can replace commercial software with open-source alternatives. We applaud them. While these efforts help trim the IT spend fat, they have little if any impact on one of the largest line items of all: staff. Said differently, CIOs should continue to pursue these initiatives, but might consider prioritizing efforts that make their staff more productive, since those efforts should move the needle more. This wasn’t always the case. In 1985, a gigabyte of storage cost $100,000. Today, it costs $0.05. In other words, it used to make sense to spend a lot of time optimizing for your hardware. By contrast, developer salaries averaged $28,000 per year in 1985. Today, developers are the new kingmakers, and they’re paid accordingly -- to the tune of $90,000 per year. Read: today it makes sense to optimize for developer productivity. Consider how this affects project costs. Take a sample project in 1985. Let’s assume in 1985 we need 5 GB of storage and we have 2 full-time developers devoted to the project. In 2013, we assume a generous 5 TB of storage and the same 2 FTEs working on the project. We take a 3-year view of cost. This is what the balance of cost looks like between storage hardware and developer salaries in 1985 and 2013. In 1985, it made sense to optimize for storage costs. Today, the cost of storage is a throwaway compared to the cost of development. In fact, the inventors of the relational database performed this calculation, too. Given the high cost of storage in their time, they made a tradeoff. They optimized the database for storage. Developer productivity, ease of use, agility -- these were deprioritized, and rightly so. Today, developers are at a premium. They comprise the lion’s share of cost relative to storage. When we built MongoDB, we optimized for developer productivity. And we’re not the only ones out to improve developer productivity. There are code collaboration tools, like GitHub. Platforms-as-a-Service, like OpenShift and Cloud Foundry. And better approaches to building apps, like agile methodologies. What your budget isn’t telling you is that old technologies are driving up your cost of development. When you budget for 2014, what are you optimizing for?
Intern Series: From MongoDB User to Return Intern - Meet Andy Mina