3 ms·
This is certainly true when solving hard problems. A counterpoint would be that most software used to run businesses is complicated, but not hard (or the hard
by lukev 8y ago
This is certainly true when solving hard problems.
A counterpoint would be that most software used to run businesses is complicated, but not hard (or the hard parts are very localized.) And for these problems it's best to factor your codebase such that it is not required to hold the whole thing in your head.
Because if you do, at some point in the project's history, someone is going to blunder in and make a change that fractures your crystal palace without you even realizing it.
- hateful 8y agoI'd say the second part of #3 is addressing this. > You can magnify the effect of a powerful language by using a style called bottom-up programming, where you write programs in multiple layers, the lower ones acting as programming languages for those above. If you do this right, you only have to keep the topmost layer in your head.
- felipemnoa 8y agoThis is pretty much how you should write programs regardless of the programming language. Otherwise the program would become virtually impossible to understand and maintain as it grows.