I would first start out with checking the code where user input is taken and then placed into SQL statements from a SQL Injection point of view, I would also take a look if user input is echoed back without any treatment to see if there are issues with XSS. If these checks yield that the previous programming done carelessly, I would call IT department to an immediate meeting to discuss this matter. At that time, you either convince the IT department that the code needs to be re-written or a great patch work is due. But many times, writing code from the ground up yields way better results than trying to fix the problematic code. I think there are two kinds of programmers. Those with do what they are told and could not care less the rest and Those who stop their bosses and guide them in the proper track. On Mon, Sep 24, 2012 at 7:05 AM, AmirBehzad Eslami <behzad.eslami@xxxxxxxxx> wrote: > Hi, > > i'm going to join a mid-size company with a few PHP-driven projects > written in procedural PHP, million years old. > > At the moment, they don't have a wiki or any documentation about their > projects. For me, the first challenge in probation period is to understand > how their code works. > * > Considering that there is no wiki or docs, How can I see the Big Picture?* > i'm sure this is a common problem for programmers everywhere. > > What approach do you use in a similar situation? > Is there a systematic approach for this? > Is there reverse-engineering technique to understand the design of code? > > Please share your experience and thoughts. > > -Thanks in advance, > Behzad -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
