Posts

Showing posts from February, 2024

Definition-by-Dysfunction

 I've done it. You've seen me. You've done it. I watched you do it. We've probably argued about it. The Defining Dysfunctions I published a blog post some time ago on the Industrial Logic website about programming together vs programming under surveillance. It's a relatively simple piece, and it identifies a problem we have in the world when it comes to just about any technique or discipline. When I suggested that people mistake group programming for working under surveillance, an incredulous reader exclaimed  “How could it possibly be anything else!?” So here's the thing: a person had a bad experience where instead of actually researching what pair programming is and how it works, they just sat down at a keyboard with another person and tried "doing pair programming" without any pre-study or preparation. They ended with one person bored, watching the other program.   This is a widely-known dysfunction or "failure pattern" known as "Work...

Listicle on Flow and Teamwork

Some article links related to solo vs group, flow, productivity, and predictability. Stop using Per-Person Swimlanes Swarming Pitfalls of solo work Programming Under Surveillance , or in groups? Faster and More Predictable Managing Interruption s Work To Be Interruptible Scatter-Gather software development What is your First Time Through ratio? Squeezing Vs Slicing Managing Programmer Productivity Over-Starting and Under-finishing