The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Seriously: Many years ago, an IBM salesman told me that when they used their very fancy tool for prototyping user interfaces, with surprisingly functional back end stub functions, they had orders from above to always leave out at least one essential function from the prototype.
The mock-up prototype was so good that several times the customer had been so satisfied with the mock-up that he said: Great, I'll take that one! - unwilling to pay for the work of developing "the real thing". But if it was fully functional, why not let them have it? Much because the demo was run at a huge mainframe, interpreting APL code. A small toy house thing runs with good enough performance, but it doesn't scale.
I really hate those projects that develop from prototype mock-ups that grow cancer and becomes completely unwieldy, because no proper future-friendly, scalable implementation architecture was ever drawn up. The prototype was created to get a go-ahead; that takes quite different qualities that a long-term architecture.
So if you consider me somewhat sceptical to the "agile" approach, there may be a grain fo truth to it
Got any tip on how I can explain that to my boss? Developer became manager trying to micromanage everything not getting me being a fan of "The right tool for the job" including "Process complexity dependent on the result complexity".
This is the best reply/question to the OP because :
1. MVC the pattern doesn't make anything more difficult. It could even be considered the beginning of OOP -- since if you think MVC (the pattern) makes things difficult you probably don't understand anything about OOP.
I converted to Microsoft's framework years ago. I believe it was still alpha, at the time. I absolutely love it. I was also trained on Java Servlet Pages in school and these used the MVC pattern and I quite like those. I have developed WebForms applications and WinForm applications as well. MVC, in any form, is a tool and you have to understand how, and where, to use it. For the vast majority of my development, it is the perfect tool. The conversion from WebForms took a bit, but once I invested the time I wouldn't return to WebForms unless I had to.
if you are referring to Microsoft's MVC.Net I love it.
It took a while for me to switch from webforms, the design pattern and extras (like routing, minifying, jquery, etc..) that get included in the starter template could be overwhelming but once I got the gist of it I never wanted to go back to webforms
It plays very nice in my mind with Xamarin, as the structure and design of an app and a webapp seem very familiar and correlate to each other
What I do not like is all of the overhead of the templates, so I will stick to developing as a SOC project that may vary within as the needs and refinements are built. One page could be MVC and another could be MVVM. Heck, my last MVC CMS actually utilizes a straight ASPX page complete with code-behind.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
I'm a great believer in the KISS principle.
We're philosophical about power outages here. A.C. come, A.C. go.