• submit to reddit
Alec Noller03/02/14
7481 views
0 replies

The Best of the Week (Feb. 21): NoSQL Zone

Make sure you didn't miss anything with this list of the Best of the Week in the NoSQL Zone. This week's best include 30 years of NBA data crunched with MongoDB, a response using PostgreSQL, thoughts on when to use GridFS on MongoDB, and more!

Alec Noller03/02/14
6102 views
0 replies

The Best of the Week (Feb. 21): Big Data Zone

Make sure you didn't miss anything with this list of the Best of the Week in the Big Data Zone. This week's best include machine learning and Flappy Bird, a how-to on using ElasticSearch from AngularJS, a collection of free books on statistical learning, and more!

Ian Mitchell02/28/14
5991 views
0 replies

Choosing Metrics for Agile Practice

In this article we look at how and why an agile team should gather elementary metrics, including lead time, throughput, velocity, and burn. We also look at cumulative flow, and briefly consider why the "actionable metrics" of the Lean Startup movement are so important to business.

Alec Noller02/28/14
5282 views
0 replies

Find Bugs in MongoDB's New Release and Win Some Prizes

In the timeless words of a great man: "It's a bughunt." Last week, the MongoDB team released MongoDB 2.6.0-rc0, and they're running a contest to find bugs. Bug "quality" is judged on severity, impact, and prevalence, and as long as you get your bug reports in by March 4th, you'll be up for some prizes.

Eric Minick02/27/14
5979 views
0 replies

DevOps for Managers Blog Series

Peter Spung (@paspung) has started a great series on DevOps speaking to the middle management layers.

Michael Täge02/27/14
7577 views
0 replies

Reporting bugs in a precise and readable way using Fail-Stories

UserStories and Scenarios used in agile methodologies are an excellent and easy-to-use way to gather requirements and to define the expected behaviour of the system in a precise and readable manner.

Mike Cottmeyer02/27/14
8525 views
0 replies

Managing Risk and Uncertainty in Agile

Okay… let’s set a little context here. In my last post we talked about two different types of projects. The ones that are knowable and the ones that aren’t knowable. Projects where it makes sense to estimate and projects that are more like R&D investments where we are spending money to learn and discover. Today, I want to talk more about the first kind. The ones where we do have some idea of what we are building and the technical challenges that might be involved.

Chase Seibert02/26/14
6061 views
0 replies

Celery fail silently context manager

Celery ships with an configuration option called CELERY_ALWAYS_EAGER which causes all tasks to be executed immediately instead of being asynchronously executed on workers. This can be very useful for unit tests. Instead of running a real message queue and separate worker processes, your unit tests can execute all in one process and still run the necessary tasks.

Gil Zilberfeld02/26/14
13348 views
4 replies

Product Roadmaps Are Anti-Agile

I was listening recently to the “Global Product Management Talk” live podcast (which I recommend, by the way). The speaker talked about creating roadmaps for product lines. It’s an interesting topic for me, as I’m juggling between products everyday. As the the interview sped along, I asked on Twitter: How are roadmaps related to agile?

Vijay Narayanan02/26/14
6553 views
0 replies

With Reusable Components Think Extend and Integrate

Many systematic reuse initiatives don’t take off the ground because of the over-emphasis on investing in a new set of components. There is all the talk and promise of enhanced productivity, reduced cost, and swift time to market – however, as focus shifts to building a library of components, real delivery suffers and business applications don’t see any material improvements.

Johanna Rothman02/26/14
4308 views
0 replies

Cost of Delay: Why You Should Care, Part 6

I’ve outlined five potential costs of delay in the previous five posts. The real problem is this: Why should you care? Maybe you have a “sweet spot” in the way you start your projects or release them. “It just takes that long here.” (That’s the sign of a system impediment.)

Alec Noller02/26/14
10019 views
0 replies

Dev of the Week: Matt Raible

Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Matt Raible, Web Architecture Consultant specializing in open source frameworks.

Nikita Salnikov...02/25/14
6133 views
1 replies

How to Estimate Memory Consumption

This story goes back at least a decade, when I was first approached by a PHB with a question “How big servers are we going to need to buy for our production deployment”. The new and shiny system we have been building was nine months from production rollout and apparently the company had promised to deliver the whole solution, including hardware. Oh boy, was I in trouble.

Dave Bush02/25/14
6168 views
1 replies

Test Driven Specifications

The gig that was suppose to be a couple of weeks long was quickly turning into a perpetual job. Soon I learned that what I was working with was a system that had a lot of bugs, but no one was willing to admit that. Eventually, frustrated by the fact that this system seemed to have a new bug every day, I asked for the specs so that I could create a test plan. That’s when I found out the worse news of all about this system: Lost Specifications.

Ian Mitchell02/25/14
5858 views
0 replies

Choosing Columns for Agile Team Boards

In this article we answer a common query about Scrum and Kanban boards: what columns should be used for tracking the progress of work items?