>Software grows until it exceeds our capacity to understand it. This point is well taken, and I think that many organization would benefit from having a CGR ro

>Software grows until it exceeds our capacity to understand it. This point is well taken, and I think that many organization would benefit from having a CGR role ("chief grim reaper"), who's job would be not to enhance the codebase or its functionality, but to do the opposite: to kill/simplify code and prevent the codebase from exceeding a certain net complexity over time. Simplicity itself need to be treated as a core feature, and the success of the CGR need to be defined by whether that core feature is maintained.