Hello fellow devs. I want your opinion about this job I ran into. I want to know if you would take the job or walk away after reading about its description.
Job
===
A large half finished php project, estimated over 60,000 lines of php, html and css.
Zero code documentation. Not even a basic entity relationship diagram.
Zero unit tests. See last point.
Developed in CakePhp 1.3 (the one compatible with php4) with a lot of code duplication, due to some validation being in controllers and not in models.
Uses subversion where all developers push and pull from trunk only.
Code has instances of raw sql injection prone code.
Managers do not want to change how anything is done, nor implement anything new. Just finish by this certain release date.
If you want to take the job, ideally explaining to the managers that their target date is unrealistic, because there current codebase was developed by someone else that didn’t follow best practices, you can’t guarantee your work because you can not depend on someone else got it right.
I can draw parallels with people in the plumbing and electrical trade, that got into similar situations and walk away.
Well depends on how much they pay, but I don’t think the stress levels would be worth it, specially if the managers are dead set on how things should be done