Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-29 Thread Jeremiah Dodds
I know this is a bit of an old topic, but I feel really strongly about this type of thing, as it's been a source of a *lot* of frustration over the years, and took me a long time to figure out something that works well for me. Some of the stuff below has been mentioned by other people, but I think

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-25 Thread AmirBehzad Eslami
Wow. David. That was a great help with every detail ! Thanks for sharing that with us. One side question: Without OOP, how do you handle Unit Tests? Do you know a Testing framework for procedural code?

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread ma...@behnke.biz
AmirBehzad Eslami hat am 24. September 2012 um 16:05 geschrieben: > 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? Hi Amir, my first start in such situations is -> phpDocument

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread tamouse mailing lists
List > Subject: Re: [PHP] Joining a team, where no wiki or docs are available > > Wow. David. That was a great help with every detail ! > Thanks for sharing that with us. > > One side question: > Without OOP, how do you handle Unit Tests? > Do you know a Testing framework fo

RE: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread Daevid Vincent
nail. Build a toolbox. ;-) From: AmirBehzad Eslami [mailto:behzad.esl...@gmail.com] Sent: Monday, September 24, 2012 12:47 PM To: Daevid Vincent Cc: PHP General Mailing List Subject: Re: [PHP] Joining a team, where no wiki or docs are available Wow. David. That was a great help with every detail

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread David OBrien
On Mon, Sep 24, 2012 at 3:06 PM, Daevid Vincent wrote: > > And for the love of [insert deity of your choice here] not EVERYTHING has > to be OOP. Use the best tool for the job!! Nothing pisses me off more than > having to instantiate a new class just to do some simple method that a > standard fun

RE: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread Daevid Vincent
> -Original Message- > From: AmirBehzad Eslami [mailto:behzad.esl...@gmail.com] > Sent: Monday, September 24, 2012 7:05 AM > To: PHP General Mailing List > Subject: [PHP] Joining a team, where no wiki or docs are available > > Hi, > > i'm going to join a

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread shiplu
On Mon, Sep 24, 2012 at 9:09 PM, AmirBehzad Eslami wrote: > Shiplu, > For debugging, what else do you use beyond xdebug and var_dump() ? Netbeans for PHP and Eclipse PDT. Both has good debugger support. An all-in-one package will server your purpose. Otherwise configuring xdebug might be painf

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread AmirBehzad Eslami
Shiplu, For debugging, what else do you use beyond xdebug and var_dump() ? On Mon, Sep 24, 2012 at 6:07 PM, shiplu wrote: > If there is no wiki there could be inline comment. If not inline comments > and those are written by your peers, dont join that team. > Even there are inline comments you'l

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread AmirBehzad Eslami
+Like. The idea of mapping the db-structure and logic behind each page is interesting. Thanks for sharing. On Mon, Sep 24, 2012 at 6:06 PM, admin wrote: > > > I would start by mapping their databases structure. > Now for each page I would map out any functions, statements or includes to

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread shiplu
If there is no wiki there could be inline comment. If not inline comments and those are written by your peers, dont join that team. Even there are inline comments you'll need to understand the architecture fast. Inline comments will help to understand a small context but not the whole For this try

RE: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread admin
> -Original Message- > 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

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread Haluk Karamete
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

Re: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread AmirBehzad Eslami
Thanks Samuel. Actually I'm not going to add features or fix bugs, they're trying a refactoring process, to improve the design of code. So, I really need to understand the current design at the outset. On Mon, Sep 24, 2012 at 5:41 PM, Samuel Lopes Grigolato < samuel.grigol...@gmail.com> wrote: >

RES: [PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread Samuel Lopes Grigolato
d.esl...@gmail.com] Enviada em: segunda-feira, 24 de setembro de 2012 11:05 Para: PHP General Mailing List Assunto: [PHP] Joining a team, where no wiki or docs are available Hi, i'm going to join a mid-size company with a few PHP-driven projects written in procedural PHP, million years ol

[PHP] Joining a team, where no wiki or docs are available

2012-09-24 Thread AmirBehzad Eslami
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. * Consideri