You have a point, but I'd say it's better to design a system for the norm rather than the exceptions. For 80-90 percent of my projects, I only have serial next actions, rather than concurrent, so this method (or something like it) would work fine. Only build in exception handling when it's really needed; otherwise, some of us who, uh, tend to prefer complicated solutions might never get started.Originally Posted by markr
There's a tenet in the XP (extreme programming) world that goes "do the simplest thing that could possibly work." A corollary to this is "you ain't gonna need it." I try to keep these things in mind when I design a new process or system for work or home.