[Discuss] php dev's code with warnings and notices

[markw at mohawksoft.com (markw at mohawksoft.com)]

Web development is a ghetto or even, still, the wild wild west. A properly
configured and developed web site with no warning would probably only
serve static web pages. If you log nothing, you miss important errors and
warnings, if you log more, you will get stupid errors and warnings.

The real issue is the cause of the errors and warnings. Some are
important, and some, simply are not.

For what it is worth, as the new senior guy, ask why you shouldn't be
worried by the errors. See if they are aware of them and understand what
they are before you cast judgment.


> Hi All,
>
> I've recently been asked to work with a team of PHP developers on a
> pretty large and complex project.  The code they have submitted works,
> but it has a bunch of warnings and notices in the logs.  I personally
> think this is sloppy coding.  My question is, how strong a stand should
> I take on this issue?  I have the senior role but I am also the "new
> guy".  I feel that code should have no warnings or notices.  But maybe
> this is not the norm?  Maybe there exists situations where it can't be
> avoided that I don't realize.  What do you think?
>
> Thanks,
> --
> Eric Chadbourne
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>