Removing The Model-View-Controller Straitjacket
pointy-stick.com
pointy-stick.com
At least with electrical engineering there are blueprints and "parts". UML does't let me work the way I think (although, when I have enough time, I don't mind it). Can anyone recommend something better than wireframing, IA, and psuedo code for code design? I think that's what's required when you need to pacify those afraid of venturing beyond MVC.
1. A whiteboard.
2. Code.
When it comes to most people's use of the term, MVC means little more than separating business logic from display logic, plus an ad hoc definition of controller.