> Most programming is actually figuring out what already exists and what (and more importantly: why) the requirements are. This is best done long before a singl

> Most programming is actually figuring out what already exists and what (and more importantly: why) the requirements are. This is best done long before a single line of code is written. Calling requirements gathering "programming" is just misusing a term for no good reason. By all means, include it in "software development" but it clearly isn't "programming".