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.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
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.