7 ms·
At the end of the day, programming is about mapping physical typing into (stored) changes in electrical signals (in transistors, capacitors, etc). The 'theory'
by nartz 12y ago
At the end of the day, programming is about mapping physical typing into (stored) changes in electrical signals (in transistors, capacitors, etc).
The 'theory' that we can somehow reduce this complexity to 'thousands of lines of code' is simply an understatement of the most profound nature. At the lowest level, the possibly vast [assembly | machine] code will have to exist.
Instead, a better viewpoint or name for this article could be 'Building extremely specified and well tested high level libraries to reduce programmer risk' - or something of that nature.
When you think about it in this way, its not different from any other library that you work with - except maybe its behavior is more understood.
- tim333 12y ago>The 'theory' that we can somehow reduce this complexity to 'thousands of lines of code' is simply an understatement... Apollo 11 managed to land on the moon with about 145 thousand lines of code so it can be done. Whether that kind of thing would be a good idea these days with vastly more capable hardware is another matter. http://www.itworld.com/article/2725085/big-data/curiosity-about-lines-of-code.html http://www.itworld.com/article/2725085/big-data/curiosity-ab...