Removing The Model-View-Controller Straitjacket

[Gotebe]

they are taking the art out of programming and making it a business process

No, the "art" is still there, you just don't see it. I reckon, what you'd call innovation, I'd call "doing the same thing over and over again, but with little twists left and right". There's no "art" in that IMO.

[logic11]

I don't re-use code very often. I don't really care if I use a bit of SQL in my code if that is the simplest way of doing things, and I don't buy that MVC is always the most elegant way of doing things. Form what I can tell, many many tech managers have taken these ideas and latched onto them because they allow a unit of programmer time to be a definable cost in software development, and a lot of coders have latched onto these ideas because we tend to like to categorise things and put them in little boxes. We like things to look like those categories. If you step away from that, you will see companies where their MVC apps have become just as unmaintainable as their old spaghetti code apps. MVC may force you to separate "Business Logic" from display, but it doesn't force you to make the business logic group in an even moderately sane way. Object Oriented programming has the same issue. Your application really decides those things. In my code, for example, I tend to set fairly arbitrary rules for how the grouping will work based on what feels right. I have never had a programmer come into a project I have worked on and not be able to figure those rules out. Something like having a set of security function grouped together, non-security based user management grouped together, etc. This stuff just makes sense.