The beauty of this is that all of your website code is in the database, making it centrally managed and all application security logic is enforced by the database.
Ah yes, the beauty of non-version controlled code stored as giant strings in the bowels of a database with the most powerful of languages (pl/sql, of course) to grease the gears. I bet it's a complete joy to use.
For indx = 1 To 3
If Not AquireResource(indx) Then
removing a lot of boilerplate code would drastically increase the cost of code maintenance.
I can't disagree more with this perspective. Anything that can be considered boilerplate (I think getter/setters on properties are a perfect example of this) should have a default implied behavior and be explicitly overridden when suitable situations arises. I gain nothing from having boilerplate code taking up mental and screen real estate when there's nothing out of the ordinary about how these elements will behave in a given context.
Similarly, I feel like there's a good deal of coding that falls in between changing the oil and manifold design.
... design, architecture, problem solving. Most of the time, those are better done in group
I disagree. As with near anything, it's a balance. Problem/designs that require deep thinking and concentration are not effectively done in a group. Often on complex problems I've found more time is spent on keeping everyone on the same page than actually addressing the problem (disk swapping, if you will). Frequent interruption to "bounce ideas" is _not_ an effective use of time as countless studies have shown. Recurring meetings are a better venue for this type of discussion, just add it to your discussion queue unless it's urgent.
once the problem is solved, anyone can implement it
Right, because writing software is just like plugging in to the quadratic equation, and any monkey or "n00b" can do it. I'm extremely curious what field you're in that you have this perspective.