Comments on: Converting Legacy Apps to CakePHP, Part 1 http://www.littlehart.net/atthekeyboard/2008/11/27/converting-legacy-apps-to-cakephp-part-1/ Facebook should've be written in unicornSchemaLang, because everyone *knows* that PHP is no good for anything, right? Mon, 09 Aug 2010 16:04:35 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Chris Hartjes’ Blog: Converting Legacy Apps to CakePHP, Part 1 : Dragonfly Networks http://www.littlehart.net/atthekeyboard/2008/11/27/converting-legacy-apps-to-cakephp-part-1/comment-page-1/#comment-11030 Chris Hartjes’ Blog: Converting Legacy Apps to CakePHP, Part 1 : Dragonfly Networks Fri, 28 Nov 2008 11:22:03 +0000 http://www.littlehart.net/atthekeyboard/?p=341#comment-11030 [...] Hartjes has started up a new series on his blog about converting legacy applications over to shiny, new CakePHP framework [...] [...] Hartjes has started up a new series on his blog about converting legacy applications over to shiny, new CakePHP framework [...]

]]> By: Chris Hartjes’ Blog: Converting Legacy Apps to CakePHP, Part 1 : WebNetiques http://www.littlehart.net/atthekeyboard/2008/11/27/converting-legacy-apps-to-cakephp-part-1/comment-page-1/#comment-11029 Chris Hartjes’ Blog: Converting Legacy Apps to CakePHP, Part 1 : WebNetiques Fri, 28 Nov 2008 11:00:33 +0000 http://www.littlehart.net/atthekeyboard/?p=341#comment-11029 [...] Hartjes has started up a new series on his blog about converting legacy applications over to shiny, new CakePHP framework [...] [...] Hartjes has started up a new series on his blog about converting legacy applications over to shiny, new CakePHP framework [...]

]]> By: AxlF http://www.littlehart.net/atthekeyboard/2008/11/27/converting-legacy-apps-to-cakephp-part-1/comment-page-1/#comment-11026 AxlF Thu, 27 Nov 2008 19:28:59 +0000 http://www.littlehart.net/atthekeyboard/?p=341#comment-11026 This is funny: I was in the similar situation. A customer asked me to extend his website... The same facts: lots of (smaller) stuff is broken, no filter on database input/output, total mixing of business and application logic, many syntax errors (e.g. to tags), also some logic was encapsulated in a class, form validation only with javascript, legacy of multiple people, lots of file.php file.php.bkp1 file.php.bkp2... And also: the application did work... i don't know how this could be true, but for their main business it worked... Unfortunatly my customer is not as wise as yours... he consists on the existing code regardless of the many disadvantages and more costs... This is funny:
I was in the similar situation. A customer asked me to extend his website…
The same facts: lots of (smaller) stuff is broken, no filter on database input/output, total mixing of business and application logic, many syntax errors (e.g. to tags), also some logic was encapsulated in a class, form validation only with javascript, legacy of multiple people, lots of file.php file.php.bkp1 file.php.bkp2…
And also: the application did work… i don’t know how this could be true, but for their main business it worked…

Unfortunatly my customer is not as wise as yours… he consists on the existing code regardless of the many disadvantages and more costs…

]]>