http://www.michiknows.com/2008/07/23/the-basics-on-using-models-and-controllers-in-php/ Insights on the IT world by Michi Kono Tue, 09 Feb 2010 12:49:54 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.michiknows.com/2008/07/23/the-basics-on-using-models-and-controllers-in-php/comment-page-1/#comment-14819 Michi Sat, 26 Jul 2008 11:57:32 +0000 http://www.michiknows.com/2008/07/23/the-basics-on-using-models-and-controllers-in-php/#comment-14819 I believe my post spends some time discussing why this form is better *over the long term*. The argument is summed up as what happens when later, new features are added? For example, maybe two check boxes... one for "remember my username" one for "remember my password"? Such a case would require you to add a fourth argument into the shorter function. Then maybe later you'll drop the remember me checkbox and replace it with a captcha, but keep the remember password one. Now do you remove the 3rd argument or do you add a 5th one or maybe shuffle arguments around? This is how spaghetti code evolves. The solution I discuss dramatically mitigates that nonsense. I didn't make it explicit in my example here, but models can be written to simply accept an array of key value pairs ($_POST). It's less verbose and a little harder to figure out what is going on behind the scenes (read: you lose some of the benefits of being explicit as I am in my examples), but it is shorter, if that's what you value. I believe my post spends some time discussing why this form is better *over the long term*. The argument is summed up as what happens when later, new features are added? For example, maybe two check boxes… one for “remember my username” one for “remember my password”? Such a case would require you to add a fourth argument into the shorter function. Then maybe later you’ll drop the remember me checkbox and replace it with a captcha, but keep the remember password one. Now do you remove the 3rd argument or do you add a 5th one or maybe shuffle arguments around? This is how spaghetti code evolves. The solution I discuss dramatically mitigates that nonsense. I didn’t make it explicit in my example here, but models can be written to simply accept an array of key value pairs ($_POST). It’s less verbose and a little harder to figure out what is going on behind the scenes (read: you lose some of the benefits of being explicit as I am in my examples), but it is shorter, if that’s what you value.

]]> http://www.michiknows.com/2008/07/23/the-basics-on-using-models-and-controllers-in-php/comment-page-1/#comment-14818 Peter Van Dijck’s Guide to Ease » Blog Archive Sat, 26 Jul 2008 08:36:54 +0000 http://www.michiknows.com/2008/07/23/the-basics-on-using-models-and-controllers-in-php/#comment-14818 [...] “Yes, my version requires the most lines of code, but it is also the easiest to maintain and understand.” [...] [...] “Yes, my version requires the most lines of code, but it is also the easiest to maintain and understand.” [...]

]]>