It seems as though there's no other way to have these discussions. My thought is that people need to be more willing to get in a heated discussion and then walk away and think on it without having permanent scars.
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.