4 ms·
I think it makes more sense if you see lines as an indicator for the thing you'll really want to minimize, which is the complexity of the model and/or instructi
by xg15 11y ago
I think it makes more sense if you see lines as an indicator for the thing you'll really want to minimize, which is the complexity of the model and/or instructions you describe in the lines.
To use a somewhat skewed analogy, imagine you want to tell directions to a foreigner.
One possible answer could be "Go 200 meters west, then go 100 meters east, then go 100 meters south".
The route that this answer describes is needlessly complex. The simpler route "Go 100 meters east, then go 100 meters south" will bring you to the same destination in less time.
You could try to further simplify you answer and just tell "Use the old road". But while that reads even shorter, you have not reduced the complexity of the actual route. It's just hidden behind an abstraction.
- talmand 11y agoI'm not against reducing complexity, I don't think that's necessarily going too far. I'm speaking more about what happens when you go too far and someone else has to deal with it. Let's say the simplest, and still descriptive, directions are: go down Main Street turn left at Oak Street turn right at Acorn Lane fifth house on the left versus: go that way, left at Smith's, right at Taylor's, brick house The second is an example of refactoring to reduce line count but actually increases complexity to someone not familiar with the area.