Re: Satellite-killing software

Subject: Re: Satellite-killing software
From: Tony Chung <tonyc -at- tonychung -dot- ca>
To: Peter Neilson <neilson -at- windstream -dot- net>
Date: Thu, 5 May 2016 08:41:30 -0700

It could also merely have been test code that wasn't removed. You know,

/* reset to dynamic data before release */
some_important_array = ["111","222","333"];
// some_important_array = db.lookup(param1, param2);

Or my favourite: the "whoops! assign instead of compare" routine:

if(logical_condition = true) ...

instead of

if(logical_condition === true) ...

These do happen.


On Thursday, 5 May 2016, Peter Neilson <neilson -at- windstream -dot- net> wrote:
> I think they commented the code and then wrote more code based upon
> reading the comments instead of the code. Only certain of the comments in
> code are good enough to instill caution and perhaps inspire a search for
> deeper understanding. My favorite one of those is this:
Visit TechWhirl for the latest on content technology, content strategy and content development |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Satellite-killing software: From: Keith Hood
Re: Satellite-killing software: From: Peter Neilson

Previous by Author: Re: integrating authored content with generated API docs
Next by Author: Re: Microsoft developer doc revamp
Previous by Thread: Re: Satellite-killing software
Next by Thread: RE: Satellite-killing software

What this post helpful? Share it with friends and colleagues:

Sponsored Ads