[m0llusk]

At a surface level programming is about coding which is like solving puzzles. But in actual application it is critical to apply a sense of judgement regarding subtleties. Which bugs are actually most important to address? When is a change enough of a fix and what more might be done to make a change the right one, possibly by making other related changes. Reducing the complex balancing act of producing usable and robust software to coding puzzles ignores the most important levels of valuable contribution.