Not sure if you'll come back and read this, but here's my current theory on structure. In a piece of software, there are many schemes by which you might organi

Not sure if you'll come back and read this, but here's my current theory on structure. In a piece of software, there are many schemes by which you might organize the source code: - Organize by author of code - Organize by chronological order of appearance (e.g. what version or patch # this appeared in) - ... by order of execution (of course, this is only a partial order) - ... by library - ... by importance - ... by some arbitrary property of the code (by algorithm, by what data it touches, etc.) Each one makes sense in a different context, and you can't have all at once. But you don't want to double-down on one choice at the expense of other, equally-valid choices with excess structure.