Re:Outside.In Scales Up - Case Study - PHP to Rails
by jamongkad on Thursday October 16, 2008 @02:52AM
(#334214)
Perhaps it's for maintenance reasons? Who knows probably the first iteration of their site was the standard PHP + SQL+ HTML format.
Re:Outside.In Scales Up - Case Study - PHP to Rails
by jbm on Thursday October 16, 2008 @08:51AM
(#334382)
Is it really that hard to create maintainable PHP code? I've been guilty of making spaghetti code myself, but after a little studying and re-learning the stuff I learned in college, I improved measurably in a matter of weeks.
It isn't so hard to write maintainable PHP code; although maybe the nature of this application was different. If they had written the rationale, I wouldn't have any of these questions :(
Re:Outside.In Scales Up - Case Study - PHP to Rails
by jamongkad on Friday October 17, 2008 @01:45AM
(#335342)
While I agree with you on your premise I'm sitting next to a guy on the cubicle to my left writing a mediumish CMS for a client in the usual PHP sort of way. Although his code is nicely indented and formatted for reading. He's having a hella of a time navigating his code base(which is like what? 3000 LOC) when the client requests for simple changes.
Without any kind of data or insight into the train of thought behind the change, this falls into the infotainment /advertising category. We can do better than this.