5 ms·

Brings up a question: what is the chance of blaming some of this on an "innocent" coding error? Can you get jail for not writing unit tests, swallowing an excep

Brings up a question: what is the chance of blaming some of this on an "innocent" coding error? Can you get jail for not writing unit tests, swallowing an exception, a type conversion you did not expect?

BurningFrog 4y ago
Interesting. The perfect crime would be to add a natural looking bug in the code that can be exploited by someone else, and then we split the money!
- gurchik 4y ago
  > The Underhanded C Contest is an annual contest to write innocent-looking C code implementing malicious behavior. In this contest you must write C code that is as readable, clear, innocent and straightforward as possible, and yet it must fail to perform at its apparent function. To be more specific, it should perform some specific underhanded task that will not be detected by examining the source code. > Every year, we will propose a challenge to coders to solve a simple data processing problem, but with covert malicious behavior. Examples include miscounting votes, shaving money from financial transactions, or leaking information to an eavesdropper. The main goal, however, is to write source code that easily passes visual inspection by other programmers. http://underhanded-c.org/ http://underhanded-c.org/
- greenonions 4y ago
  Genius, but it has to be a bug that you haven't knowingly prevented before, otherwise it'd be suspicious.
deleted 4y ago
[deleted]
polygamous_bat 4y ago
I believe that really depends on (a) how much harm it caused downstream, (b) how much of it is caused by your actions. Per Matt Levine's column today, it's not the whole problem that FTX had sloppy accounting – rather that SBF went around advertising the "sophisticated risk engine" which in reality was crap. This action accounts for fraud. I don't see you being jailed for your random GitHub project being sloppy. However, if your closed source software that you advertise as 100% safe and secure gets used by a chemotherapy clinic, and then it comes out to be downright sloppy after killing 20 patients you may be accused of fraud. Anyway, not a lawyer so take it with a grain of salt.
- gcr 4y ago
  I hope it also depends on a reasonable expectation of oversight and access controls when you're working in high-risk fields. Finance engineers should probably be expected to be familiar with laws concerning what they do.
- 8note 4y ago
  The relevant deadly chemotherapy example: https://youtu.be/Ap0orGCiou8 https://youtu.be/Ap0orGCiou8
siva7 4y ago
Zero Chance. Singh already proved intent with his source code comment. Him claiming to be unaware of violating the law won't prevent him from getting almost certainly jailed.
- Gigachad 4y ago
  Seeing all the crypto bros go to jail is the heart warming start to 2023 I needed.

BurningFrog 4y ago

Interesting. The perfect crime would be to add a natural looking bug in the code that can be exploited by someone else, and then we split the money!

gurchik 4y ago
> The Underhanded C Contest is an annual contest to write innocent-looking C code implementing malicious behavior. In this contest you must write C code that is as readable, clear, innocent and straightforward as possible, and yet it must fail to perform at its apparent function. To be more specific, it should perform some specific underhanded task that will not be detected by examining the source code. > Every year, we will propose a challenge to coders to solve a simple data processing problem, but with covert malicious behavior. Examples include miscounting votes, shaving money from financial transactions, or leaking information to an eavesdropper. The main goal, however, is to write source code that easily passes visual inspection by other programmers. http://underhanded-c.org/ http://underhanded-c.org/
greenonions 4y ago
Genius, but it has to be a bug that you haven't knowingly prevented before, otherwise it'd be suspicious.

deleted 4y ago

[deleted]

polygamous_bat 4y ago

I believe that really depends on (a) how much harm it caused downstream, (b) how much of it is caused by your actions. Per Matt Levine's column today, it's not the whole problem that FTX had sloppy accounting – rather that SBF went around advertising the "sophisticated risk engine" which in reality was crap. This action accounts for fraud. I don't see you being jailed for your random GitHub project being sloppy. However, if your closed source software that you advertise as 100% safe and secure gets used by a chemotherapy clinic, and then it comes out to be downright sloppy after killing 20 patients you may be accused of fraud. Anyway, not a lawyer so take it with a grain of salt.

gcr 4y ago
I hope it also depends on a reasonable expectation of oversight and access controls when you're working in high-risk fields. Finance engineers should probably be expected to be familiar with laws concerning what they do.
8note 4y ago
The relevant deadly chemotherapy example: https://youtu.be/Ap0orGCiou8 https://youtu.be/Ap0orGCiou8

siva7 4y ago

Zero Chance. Singh already proved intent with his source code comment. Him claiming to be unaware of violating the law won't prevent him from getting almost certainly jailed.

Gigachad 4y ago
Seeing all the crypto bros go to jail is the heart warming start to 2023 I needed.