Forum Moderators: coopster
Why cant webmaster php team instigate the idea of coming up with a book of errors produced by codes. I think it would sell quite well because i would certainly purchase a copy... sometimes you want analyse things away from the computer...
what do people say?
A book? I dunno... this thought keeps coming back to me. I once wrote and published a book of poetry. In the end far more of those books were given away than were sold. Why? There isn't enough interest. As a programmer I would much rather spend my time reading a book that helps me develop good code over a book that might point out my glaring deficiencies. And I learn faster from my own mistakes than from anothers mistakes.
I actually have given some thought to presenting some of the most obvious errors and what can cause them. In the end, however, most people with a problem will not read archived information. The problem is now, and they want a solution now. Most professionals know how to research a problem, and they also already know most of the problems and how avoid them in the first place. The rest of us freak out when an error arrives and rush off to the nearest forum seeking a solution (I'm guilty too).
Given all that, your idea is still not a bad idea at all. An example where this has been done would be included in the documentation that arrives with your brand new (or refurbished) AS/400 from IBM (not a plug - just experience). A complete set of books will contain several books with error code information. But the scale of PHP vs. IBM is quite different.
