What about using visual code coverage instead of callstacks? I think the big picture is easier to digest. Maybe a combination of both, as code coverage won't provide the "time" axis of the monster.
Something like http://phpcoverage.sourceforge.net/ -----Mensagem original----- De: Mihamina Rakotomandimby [mailto:miham...@rktmb.org] Enviada em: segunda-feira, 24 de setembro de 2012 11:58 Para: PHP General Assunto: Re: [PHP] Re: Joining a team, where no wiki or docs are available On 09/24/2012 05:38 PM, AmirBehzad Eslami wrote: > #1 Start using the software as an End-User (don't care about the code) > to understand the business-value of the software > #2 Take a look at the database scheme, try to understand the entities > and their relations > #3 As you use the software, you'll become more curious about its > features and how they've implemented. > #4 Start to see how they've implemented common problems, such as: > Authentication, CRUD, etc. How the other interesting features are > implemented #5 install xdebug + geben + emacs and have a look at the call stacks and bottlenecks. -- RMA. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
