Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #67427
| From | Alister <alister.ware@ntlworld.com> |
|---|---|
| Subject | Re: posting code snippets |
| Newsgroups | comp.lang.python |
| References | <e77aff42-6ec3-4749-9683-6ebb2a33ac1a@googlegroups.com> <85ppm8nqx7.fsf@benfinney.id.au> <mailman.7458.1393566098.18130.python-list@python.org> <leq6j9$mnb$2@reader1.panix.com> <mailman.7542.1393712199.18130.python-list@python.org> |
| Message-ID | <LyEQu.14090$Yn3.13272@fx29.am4> (permalink) |
| Organization | virginmedia.com |
| Date | 2014-03-02 11:25 +0000 |
On Sun, 02 Mar 2014 09:16:35 +1100, Chris Angelico wrote: > On Sat, Mar 1, 2014 at 1:31 AM, Grant Edwards <invalid@invalid.invalid> > wrote: >> You drag out the lab scope, logic analyzer, spectrum analyzer, sweep >> generator, strip plotter, and the machine that goes "ping". You start >> to get everything set up to nail that problem securely to the >> dissecting board. Long before you actually get to that point, the >> problem becomes intimidated and reveals itself and a solution. > > *ALL* my machines go ping. It's fundamental to network debugging. I know > that's not what you meant, but somehow it comes to the same thing. :) > > And yep. That is so absolutely right. Problems know when concealment > becomes pointless. > > ChrisA As a maintenance engineer I find there is also an opposite factor in operation. Equipment manufacturers appear to include an "Engineer Proximity Detector" in all designs that cause the equipment to work flawlessly when triggered. The issue the customer has been complaining about incessantly never occurs whilst there is an engineer on site. -- We're out of slots on the server
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 04:13 -0800
Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-02-27 23:27 +1100
Re: posting code snippets Jerry Hill <malaclypse2@gmail.com> - 2014-02-27 10:01 -0500
Re: posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 07:23 -0800
Re: posting code snippets Tim Chase <python.list@tim.thechases.com> - 2014-02-27 09:56 -0600
Re: posting code snippets Ben Finney <ben+python@benfinney.id.au> - 2014-02-28 09:15 +1100
Re: posting code snippets "Mark H. Harris" <harrismh777@gmail.com> - 2014-02-27 15:13 -0800
Re: posting code snippets Dave Angel <davea@davea.name> - 2014-02-28 00:05 -0500
Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-02-28 16:41 +1100
Re: posting code snippets Grant Edwards <invalid@invalid.invalid> - 2014-02-28 14:31 +0000
Re: posting code snippets Gene Heskett <gheskett@wdtv.com> - 2014-03-01 16:55 -0500
Re: posting code snippets Chris Angelico <rosuav@gmail.com> - 2014-03-02 09:16 +1100
Re: posting code snippets Alister <alister.ware@ntlworld.com> - 2014-03-02 11:25 +0000
Re: posting code snippets Gene Heskett <gheskett@wdtv.com> - 2014-03-02 07:20 -0500
Re: posting code snippets Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-03-02 17:20 +1300
csiph-web