Earlier quoted context omitted.
> architect stuff how can someone be good at architect-ing stuff if they never code or code very little. seems like the method GP is describing would be good to weed out such imposters.
They've coded for 10 or 20 years, and now just sit back and design interfaces, write specs, evaluate technologies, mentor juniors, do code review, and of course the ultimate mind blow when you're trying to figure out who to fire: they remove code instead of add it. Unfortunately for the company, these "imposters" do indeed get weeded out in preference to the recent college grad copy/pasting thousands of lines of Stac…
If you can remove code from your code base without hampering the functionality, that's usually a much better time investment than writing new code.