I don't think it's an underclass. There's a group of people who does not want to be *bothered* with the details of "low level programming" while they can still make valuable contributions to application development. This group of people will never grow into a full blown programmer, because they're just not interested in becoming one, but why would I want to lock them out while they can do valuable work?

Not all applications need to scale up, nor do they need to scale up right away. Getting some small feature in place right away is often more important than making sure it's scalable right from the start. I know that's your concern, Chris, and it's also one of mine, but it depends entirely on the circumstances whether it's an important one. Sometimes implemented badly but working *now* is sometimes more important than it being scalable but later. I just want to at least make this pattern of development more *maintainable* than it's been in the past. I think it should be possible to reduce the maintenance cost of their contribution while still allowing it.

I don't know exactly how big this group is and what they'd be satisfied with. I think there are different use cases involved and they have different solutions. UML code generation, ability to tweak HTML and simple logic, and some scripting functionalities may be answers to slightly different, though related, problems.