Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "mvc design pattern"
Legends -> I: Interviewer
I: what is mvc architecture
Me: model.. view.. controller... and blah blah
I: mvc is not an architecture.. its a design pattern.. architecture is blah blah
I: srry U r rejected.. god bless you
Me: googled 'Is mvc a design pattern or architectural pattern'
Google: shows stack overflow link
Stackoverflow: mvc is architectural pattern blah blah... accepted answer
Me: hopeless about my future
GOD BLESS THE INTERNET and SOFTWARE DEVELOPERS18
Just "learned" that Singleton is a good design pattern with no disadvantages. And in MVC the model should be a singleton.
Reading comments here and subsequently looking here I’m wondering if I’ve been doing MVC wrong. I’ve always thought the View calls data from the Model. However I see people load model data and then call the view via the controller.
Which is right?2
My model for one part of my project has become so crazy big I’m become lost every time I add a new feature or debug :-/