Nick seems to define a Mort as:
Mort works in a small to medium sized company, as a guy who uses the tools at hand to solve problems. If the business needs some data managed, he whips up an Access database with a few reports and hands it to the three users who need the data. He can write Excel macros and he's probably found in the late afternoons on Friday updating the company's one web site using Frontpage.
Mort is a practical guy. He doesn't believe in really heavy processes. He gets a request, and he does the work.
So far, he is following the same well known path of describing Mort. The problem is that he then seems to decide that Mort is a super agile guy. Take a look at Sam Gentile's comment:
MSFT is making tools for Morts (the priority) at the expense of every other user (especially Enterprise Developers and Architects). They have nothing for TDD. And I would further contend that making these tools "dumbed down" has significantly contributed to why Morts are Morts in the first place and why they are kept there.
And Nick's response:
Wow, Sam. I didn't know you had so much animosity for the Agile community! Are you sure that's what you intended to say?
Do you really mean that Microsoft should make a priority of serving top-down project managers who believe in BDUF by including big modeling tools in Visual Studio, because the MDD people are more uber-geeky than most of us will ever be? I hate to point this out, Sam, but Alpha Geeks are not the ones using TDD. It's the Morts of the programming world. Alpha geeks are using Domain Specific Languages.
I really have no idea how to respond to such a claim. It certainly doesn't match my experience.