3 ms·

I've rarely seen people fail to realize that having at on of code in a really fat layer is a problem. I've seen lots of people fail to separate that code in a

I've rarely seen people fail to realize that having at on of code in a really fat layer is a problem. I've seen lots of people fail to separate that code in a clean and extensible manner. The result is a still-fat layer that's split across a bunch of different files and methods. But every piece is still concerned with almost every piece of context that was originally passed into the controller. Composability and separation of concerns are the answer, but it's much more of an art than something I've ever seen a simple tutorial for. It's gonna look different for different business cases.

tabtab 7y ago
Re: It's gonna look different for different business cases. Conway's Law rules. We need constructs that easily help us fit the stack to our teams and shop conventions. MVC allowed a shop to throw masses of people and code at a problem instead of removing the need for masses of people and code. The web made a mess out of CRUD app programming and MVC was a first step in taming the mess, but it requires fat staffing and lots of specialists to manage the screwy parts.