I agree in principle, but at some point you're done with don't-repeat-yourself framework wizardry and you're up against the basic task of translating fragmentary verbal requirements into a technical solution. Web frameworks (sometimes) make that process more productive but no less boring.
That's true, but I think we can both agree that the author can do a lot better than spending 60% of his time to "copy-and-paste chunk of code, then tweak for new field names, then make sure to update the correct database fields, add validation, ad nauseum."
