Re: How do you handle debug code? Removing from production versus conditional execution
Jerry Stuckle <[email protected]> Mon, 24 Apr 2023 14:27:03 -0400
| Newsgroups | comp.lang.php |
|---|---|
| Organization | A noiseless patient Spider |
| Message-ID | <[email protected]> |
On 4/24/2023 1:50 PM, Richard wrote: > [Please do not mail me a copy of your followup] > > [email protected] (The Doctor) spake the secret code > <[email protected]> thusly: > >> This abusive spamtroll came from > > You're only making it worse by responding to their posts. Either > report the abuse to their posting ISP or adjust your KILL file to drop > their posts so you don't see them. > > To answer the real question from 2019 (whee!), instead of addding > "debug" code to your production deployment, write unit tests for > everything you do so that you have confidence in the deployed code. > > An example can be found here: > <https://github.com/LegalizeAdulthood/manx> Actually I don't have a problem with The Doctor calling out the posting ISP. But I wish he wouldn't copy the entire message. It just gives the message more popularity. -- ================== Remove the "x"'s from my email address Jerry Stuckle [email protected] ==================