Originally posted by TheCotMan
Which is trusting your compiler to not leave too many clues about your encryption cipher implementation?
But I would say unsound cryptography lies in the "math is hard" domain, and you can say similar things about compilers (especially in Lisp and other functional languages where compilation is truly a mathematical transform)
Consider design decisions.
Consider the notion that even the best coders have a single project limit where they understand all of the pieces at the same time of about 10k lines of code.
I am not so sure the device would make our math better.
A sharing of thoughts does not increase the maximum capacity we have to fully understand all the parts of a project in under 10k lines of code.
Now. Consider the number of lines of code in MS Windows XP and estimate how many lines of machine code that would be.
Consider what would be required for a person to understand the whole project.
You apply an additive effect to "help" the process, but don't apply it to errors. The Mythical Man Month shows us effects of adding people to a project; it does not leaad to linear growth to code productivity. Adding more brains to a project can slow it down. Allowing bad ideas to pass directly? Such effects would be subject to an additive effect as well.
I think the best application of transmitting thoughts would be education.
Comment