Programming Practices

I suppose McNeel comes up against this too…

Thanks for all, RMcN

Indeed, though I don’t think anyone here has made a graph yet.



There is a constant healthy tension between three competing forces in any software development project:

  1. Time
  2. Resources (people, money, computing power)
  3. Work to be done

We have always had way more work to do than time or resources. We strive to listen to customers, which always adds to our to-do list. That’s where the art of prioritization comes in. Not all things are created equal, but we often remember the person associated with a request, and feel bad when we have to relegate it to the “future work” pile.

Within the “work to be done” section, there’s also a tension between “shiny new things” and “fixing up broken old stuff”. Both matter to our customers.