• submit to reddit
Mitch Pronschinske02/13/13
0 replies

DZone Links You Don't Want To Miss (2/13/13)

One developer shop finds a great way to get back at a customer that stole their work. Also an MIHTool that will change your life. Plus news about JavaFX, and an XKCD-style comic maker.

John Sonmez02/12/13
6 replies

We Can’t Measure Anything in Software Development

The interesting thing about Baccarat is that despite the odds, despite common sense, despite the understanding that the game is completely random, people will still sit there and record every single hand and score trying to use it to look for patterns to predict future results. Programming is similar.

Sandro Mancuso02/12/13
5 replies

Frustrations and Aspirations of a Software Craftsman

For a while I've been thinking about what makes me like or dislike a project. Having spent a very big part of my career working for consultancy companies, I was exposed to many different environments, industries, team sizes, processes and technologies.

Steve Rogalsky02/12/13
0 replies

How to Prioritize a User Story Map

It is no wonder that when Jeff Patton showed me how to create a user story map and use it to create thin application slices to prioritize agile projects effectively that I was hooked.

Mitch Pronschinske02/12/13
0 replies

DZone Links You Don't Want To Miss (2/12/13)

More security woes for Ruby on Rails and a new core API server for Chef, made with Erlang. Plus Memcache on SSD and DNS art.

Martin Harris02/12/13
0 replies

6 Tips for Good Scrum

If you are doing these, then you're doing very well at Scrum indeed, and are likely to get better over time.

Paul Underwood02/11/13
0 replies

Using The New Twitter API V1.1

From March 5th 2013 Twitter are removing there current API and it will be fully replaced with the new API V1.1. This means that any application that is currently using the old API will stop working on March 5th. The main feature of the API is that requests need to be authenticated before they will work correctly.

Cagdas Basaraner02/11/13
2 replies

Must-Read Books for Software Engineers

This list of books covers references, craftsmanship, refactoring, patterns, and project management.

Kane Mar02/11/13
0 replies

Excerpt from Scrum 101: Scrum and XP

This is the second excerpt from Scrum101, the free intensive online introduction to Scrum, which I introduced several weeks ago. In this second except, I’d like to share the most popular Scrum 101 lesson at the moment.

Mitch Pronschinske02/11/13
0 replies

DZone Links You Don't Want To Miss (2/11/13)

IoC Containers are considered harmful to this lead developer. And Windows 9 predictions are already out there. Plus the top 10 open source rookies from 2012 and 20 free Scrum project management tools.

Mitch Pronschinske02/10/13
0 replies

ZeroMQ: Popular and Controversial

I found a very good review of ZeroMQ from Pieter Hintjens, a veteran in distributed software. He not only had a strength and weakness review of ZeroMQ, but he also had an interesting and critical take on a popular message queue, RabbitMQ.

Johanna Rothman02/09/13
0 replies

Agile Lifecycles for Geographically Distributed Teams, Part 3

Here's another example of distributed teams that shows how helpful a Kanban board can be. It lets you know, for example, if the developers are producing more than the testers can handle.

Mitch Pronschinske02/08/13
0 replies

DZone Links You Don't Want To Miss (2/8/13)

An article by a Cornell professor sparks a debate about MongoDB's fault-tolerance, and we get to see how the CEO of Evernote gets things done. Plus Drupal 8 gets a new default editor and the greatest CSS3 demo of all time arrives!

Johanna Rothman02/08/13
0 replies

Agile Lifecycles for Geographically Distributed Teams, Part 2

A second example of geographically distributed development organizations. This example will show you how to use a project manager with Kanban and teams in silos.

Johanna Rothman02/08/13
0 replies

Agile Lifecycles for Geographically Distributed Teams, Part 1

I’ve been working with geographically distributed and dispersed teams for the past couple of years. Some of them on quite large programs, some of them reasonably small. What they all have in common is that they all want to transition to agile.