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
Jim wrote:
If you really are joining a team, I would expect that the teammates
would
be guiding you through their systems.
True, but based on my experience, most programmers are not good when it
comes
to explain stuff. So, I should rely on my own.
On 09/24/2012 05:19 PM, AmirBehzad Eslami wrote:
True, but based on my experience, most programmers are not good when it
comes
to explain stuff. So, I should rely on my own.
Choose another team?
--
RMA.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit:
That's like erasing the question from the paper, in order to give it a
solution!
I was thinking about this problem for a while, and I've ended-up with this
approach:
#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
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
Never worked with Emacs or genben. I'm a fan of vim ;)
But thanks a ton, based on your suggestion, I just found vim-dbgp
On Mon, Sep 24, 2012 at 6:27 PM, Mihamina Rakotomandimby miham...@rktmb.org
wrote:
#5 install xdebug + geben + emacs and have a look at the call stacks and
bottlenecks.
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
7 matches
Mail list logo
