[wvenable]

My whole line of thought actually comes from misunderstanding the point of the article. My original reading was that it was dismissive of jumping in and coding as a method of working out requirements -- which I disagree with it. I think jumping in and coding is one good way (but not the only way) to work out requirements with stakeholders.

Instead the article is about programmers who code without the involvement of stakeholders at all. The inclusion of agile is a bit of red herring.