Link Details

No MDA any more!

What a strange reply. It looks like you didn't even read the article. There are many very good reasons to use MDA. Please read something first before adding comments.

I absolutely don't believe that carefully-prepared laundry list. MDA puts the programmer totally out of control and makes the learning curve incredibly steep for someone new joining the team. Not only does it make the code base unwieldy, you also get locked into a certain tool set that mostly won't integrate with your IDE. I am telling this from experience.

>MDA puts the programmer totally out of control and makes the learning curve incredibly steep for someone new joining the team.
In my experience this is not the case. See also my comment on the article about the roles in an MDD project team.

> you also get locked into a certain tool set that mostly won't integrate with your IDE
A lot of the current MDD tools are based on Eclipse and integrate seamlessly with Java programming.

Blah blah blah. There's no silver bullet. Your secretary can't write an enterprise application no matter how much you want this to be the case.

There's indeed no silver bullet. That's why the article also points to other articles talking about the dangers / challenges of MDD.

> Your secretary can't write an enterprise application no matter how much you want this to be the case.
Agreed. You will need some affinity with IT, you will need training for the MDD tool. The only point the article makes is that you do not have to be a specialist, e.g. a database expert, or to have knowledge about Spring (or other frameworks). You use models, and the plumbing is done by the MDD tool.

POJO + MDD

No damn xml, scripts, configuration files, learning new twisted methods of doing things


POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO POJO