I'm a professional PHP, Python and Javascript developer from the UK. I've worked with Django, Laravel, and React, among others. I also maintain a legacy Zend 1 application.
It's absolutely abysmal. It's an old Zend 1 project that has seen at least two attempts at a rewrite fail,and at one point went off to another agency for a year or two before coming back. Until I started on it, it had no tests, and the JavaScript was all spaghetti jQuery. Almost everything was crammed into fat controllers, and there was a huge amount of duplication (12% if you didn't include the view layer, according to PHPCPD). The models were used as both domain objects and repository-style classes, so to find an item by ID, you had to create a new object, then call find() on it to get that item.
But, it's teaching me a LOT about working with legacy code, refactoring and implementing design patterns.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It's absolutely abysmal. It's an old Zend 1 project that has seen at least two attempts at a rewrite fail,and at one point went off to another agency for a year or two before coming back. Until I started on it, it had no tests, and the JavaScript was all spaghetti jQuery. Almost everything was crammed into fat controllers, and there was a huge amount of duplication (12% if you didn't include the view layer, according to PHPCPD). The models were used as both domain objects and repository-style classes, so to find an item by ID, you had to create a new object, then call find() on it to get that item.
But, it's teaching me a LOT about working with legacy code, refactoring and implementing design patterns.