7 ms·
For the analogy you're drawing to really hold, we have to picture a computer where the bytes get a lot of work done on their own and our code merely exists to s
by savanaly 9y ago
For the analogy you're drawing to really hold, we have to picture a computer where the bytes get a lot of work done on their own and our code merely exists to slow down and redirect their efforts (in other words, a negative and a possible positive). If you were concerned with the fast, efficient operation of the computer then you might indeed want a rule like "one in, one out" for lines of code.
- RugnirViking 9y agoWhen space was limited in game cartridges in the past I can imagine such a rule actually existing in a real buisness setting. One line of code in, one line of code out. That would lead to some really weird software, and it would take longer, but it would probably improve the software in some metrics like performance