aki wrote:
Many thnks for the replies. I'm not the one interested but looking at the Job Description requirements that Moses had listed, it was interesting that corporate/enterprise/project management developer tools should be available to those in such enviroments.
Not sure I should comment too much on specifics, but I believe that Moses and his team have been working with a setup similar to the one I described previously (at least at one point in time)...
Question : What about de-bugging? Do the tools you mention provide extensive de-bugging?
Debugging - now thats always a challenge - the hardest problems to debug is of multithreaded nature, and since PHP by default is stateless many of these problems are avoided all together... Fortunately we work a lot with Taesk CMS, and build into our Taesk development setup we have several debugging facilities. Every sql query we execute in our development setup is automatically analyzed and any (potential) index problems are shown immediately to the developer. Similar we have several build in performance counters that can give us various measurements, which can be used as hints to where a problem might reside (mainly performance wise). As to the more "regular" bugs, we tend to generally rely on print statements.. More interesting however is how the bugs are avoided in the first place - any ideas ? Regards Michael Pedersen PLUSPEOPLE