Re^3: Why Scaffolding? Validation and learning.

Anything that helps me move more quickly from data model diagram to finished app is a winner.

What about the maintainability of that application?

Comment on Re^3: Why Scaffolding? Validation and learning.

Replies are listed 'Best First'.
Re^4: Why Scaffolding? Validation and learning. by philcrow (Priest) on Aug 22, 2006 at 14:20 UTC
Perhaps my initial comment was a bit abbreviated. My main point is that a good generator benefits experienced users as much or more than it benefits newcomers looking for a quick peek at a framework they might want to use. My particular generator (Bigtop) spends a great deal of effort to split the code it makes into that which is likely to change and that which you modify with your own code. This aids maintenence since you can continue to regenerate to good effect even after initial production deployment. We did this recently in an ORM migration. Bigtop did about half the work in the first hour. I did the rest over the next week or so. Phil	[reply]

Replies are listed 'Best First'.

Re^4: Why Scaffolding? Validation and learning.
by philcrow (Priest) on Aug 22, 2006 at 14:20 UTC

My particular generator (Bigtop) spends a great deal of effort to split the code it makes into that which is likely to change and that which you modify with your own code. This aids maintenence since you can continue to regenerate to good effect even after initial production deployment. We did this recently in an ORM migration. Bigtop did about half the work in the first hour. I did the rest over the next week or so.

Phil

[reply]