Re: Joining a team, where no wiki or docs are available
| From: | Jim Giner | Date: | Mon, 24 Sep 2012 14:15:31 +0000 |
| Subject: | Re: Joining a team, where no wiki or docs are available | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-319221@lists.php.net to get a copy of this message | ||
On 9/24/2012 10:05 AM, AmirBehzad Eslami 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 If you really are joining a team, I would expect that the teammates would be guiding you through their systems. If only to ensure that you are becoming productive.