Troubleshooting & Instrumentation
Anyone who works in software engineering has to deal with troubleshooting failures. Personally I like to approach failures as a challenge, a kind of treasure hunt that when complete leads you to the cause of the problem. This is great when all of the clues are there, but what happens when some are missing? You might get to a point where you can see multiple different paths to the end. You might also be led in the totally wrong direction and spend an unnecessary amount of time finding your way back to the path.
Processes Through an Outcome Lens
Processes are vital to modern organizations. Imagine you were asked to help improve an organization, and found that it had zero defined processes. You’d almost certainly start by implementing a process or two, then by wondering how in the world they got along without any processes.
Pre-modern organizations likely had their own processes as well. As organizations began to grow, ad-hoc behavior became less effective.
Our Path to Mobbing
This is an experience report from our team, who first dabbled with mob programming two years ago; since then we have adopted it as part of our core culture, and continue to spread it throughout our organization and clients. We talk a bit about who inspired us, how we convinced our leaders to let us try it, and where we ended up. We also show some of the data we collected along the way, and talk about the advantages we’ve seen, the challenges we’ve encountered, and some of the ways we’ve adapted.