Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: Preparation for what's coming |
| Date | 2015-10-07 11:43 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <mv2pcq$bf$1@dont-email.me> (permalink) |
| References | <fcd1907e-026f-4c37-87ea-2b92e76c86f1@googlegroups.com> <662d3687-975c-4c0f-833e-d9ddd0ba85c2@googlegroups.com> <d86ae031-df67-4120-a0e2-17a62a8c59c6@googlegroups.com> <mv1d3m$aeu$1@speranza.aioe.org> |
On 06/10/15 23:05, glen herrmannsfeldt wrote:
> Malcolm McLean <malcolm.mclean5@btinternet.com> wrote:
>> On Tuesday, October 6, 2015 at 3:55:51 PM UTC+1, Rick C. Hodgin wrote:
>>> See an updated / expanded version located here:
>
>> The main headline on Sept 23 was a story about a car manufacturer
>> cheating on nitrous oxide emissions tests.
>
> It is on all oxides of nitrogen, not just nitrous oxide.
> Nitric oxide and nitrogen dioxide are important contributors
> to smog, and harmful to humans (and other animals and plants).
>
>> An important story, but hardly anything of shattering historical
>> importance. You were wrong.
>
> It does bring up some important points in regard to computer
> programming and liability. It isn't so obvious yet how high
> up it went, but there is pretty much no doubt that those
> writing the software knew what they were doing.
>
> Now, consider that such software engineers might want to
> get jobs somewhere else. Will you trust them with your project?
>
You can be sure that the software developers were doing what they were
told by the company (or department) leadership, not by their own
initiative. It is conceivable that they did not even know there was
cheating involved, if the tasks were divided up enough.
Such software cheats are not new (well, since this one apparently goes
back to at least 2008, it's not new either). For a while it was common
in graphics drivers - they detected that the user was running a known
benchmark program, and cheat in some way in order to give apparently
faster results. And it has been known for compiler developers to
"optimise" their tools for "special cases", such as SPEC_INT benchmarks.
And cheating, or law-breaking of various sorts, is certainly nothing new
amongst professionals. In some professions, such as the medical and
legal professions, you need to be licensed and the license involves
oaths against such unethical behaviour. This gives them extra
protection against being asked to do something questionable. But for
most people, there is no such thing. Your boss tells you to make the
changes, or be fired ("and you'll never work in this town again").
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-18 08:34 -0700
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-18 19:40 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-18 10:52 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-18 12:48 -0700
Re: Preparation for what's coming Steven Hystad <steven.hystad@lunarinfrastructure.net> - 2015-09-22 19:22 -0600
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 13:09 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 13:13 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 13:48 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 14:19 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 14:50 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 14:56 -0700
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-20 00:11 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 15:24 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-20 00:37 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-20 00:44 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-20 22:26 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-21 08:31 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-22 10:38 +0200
Re: Preparation for what's coming gazelle@shell.xmission.com (Kenny McCormack) - 2015-09-22 08:44 +0000
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-22 10:59 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-22 02:50 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-22 03:09 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-22 07:51 -0700
Re: Preparation for what's coming "James Harris" <james.harris.1@gmail.com> - 2015-09-22 20:34 +0100
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 10:17 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-23 01:45 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-23 08:50 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-23 11:10 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-24 16:11 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-24 08:17 -0700
Re: Preparation for what's coming James Kuyper <jameskuyper@verizon.net> - 2015-09-24 12:17 -0400
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-24 10:52 -0700
Re: Preparation for what's coming BruceS <bruces42@hotmail.com> - 2015-09-22 16:39 -0600
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 16:01 -0700
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-23 11:08 +1200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 16:30 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 10:38 +0200
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-23 21:32 +1200
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-23 03:04 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-09-23 13:10 +0200
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-21 11:55 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 15:27 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-09-20 01:02 +0200
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:13 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-09-20 02:28 +0200
Re: Preparation for what's coming Siri Cruz <chine.bleu@yahoo.com> - 2015-09-19 18:26 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:19 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-19 16:28 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-19 17:23 -0700
Re: Preparation for what's coming Keith Thompson <kst-u@mib.org> - 2015-09-19 18:26 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 20:25 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-19 20:38 -0700
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-09-20 15:57 +1200
Re: Preparation for what's coming jacobnavia <jacob@jacob.remcomp.fr> - 2015-09-21 10:46 +0200
Re: Preparation for what's coming Jens Stuckelberger <Jens_Stuckelberger@nowhere.net> - 2015-09-20 23:37 +0000
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 13:04 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 13:19 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-21 14:12 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 14:22 -0700
Re: Preparation for what's coming Rosario19 <Ros@invalid.invalid> - 2015-09-22 00:37 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 15:41 -0700
Re: Preparation for what's coming Rosario19 <Ros@invalid.invalid> - 2015-09-22 00:54 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-21 16:03 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-22 03:09 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 03:49 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 04:12 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-22 04:14 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-22 04:45 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-09-23 12:24 -0700
Re: Preparation for what's coming fir <profesor.fir@gmail.com> - 2015-09-23 13:16 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-09-24 11:25 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-09-22 12:44 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 06:21 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 07:55 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-06 09:09 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 09:14 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 09:16 -0700
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-10 21:26 -0700
Re: Preparation for what's coming "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-10 23:45 -0700
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-11 00:31 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-10-11 13:36 +0200
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-10-11 21:35 +1300
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-11 06:10 -0700
Re: Preparation for what's coming Melzzzzz <mel@zzzzz.com> - 2015-10-11 15:38 +0200
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-11 07:59 -0700
Re: Preparation for what's coming glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-06 21:05 +0000
Re: Preparation for what's coming Malcolm McLean <malcolm.mclean5@btinternet.com> - 2015-10-07 00:59 -0700
Re: Preparation for what's coming David Brown <david.brown@hesbynett.no> - 2015-10-07 11:43 +0200
VW (Re: Preparation for what's coming) Jorgen Grahn <grahn+nntp@snipabacken.se> - 2015-10-07 13:33 +0000
Re: VW (Re: Preparation for what's coming) glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-10-08 01:04 +0000
Re: Preparation for what's coming Ian Collins <ian-news@hotmail.com> - 2015-10-07 08:32 +1300
Re: Preparation for what's coming "Rick C. Hodgin" <rick.c.hodgin@gmail.com> - 2015-10-06 12:46 -0700
csiph-web