Merge pull request #1421 from tigerbeetle/matklad/main-on-top

style: main on top

Author: matklad

Diff for: docs/TIGER_STYLE.md

@@ -273,6 +273,13 @@ Beyond these rules:
 * Callbacks go last in the list of parameters. This mirrors control flow: callbacks are also
   _invoked_ last.
 
+* _Order_ matters for readability (even if it doesn't affect semantics). On the
+  first read, a file is read top-down, so put important things near the top. The `main` function
+  goes first.
+
+  At the same time, not everything has a single right order. When in doubt, consider sorting
+  alphabetically, taking advantage of big-endian naming.
+
 * Don't overload names with multiple meanings that are context-dependent. For example, TigerBeetle
   has a feature called *pending transfers* where a pending transfer can be subsequently *posted* or
   *voided*. At first, we called them *two-phase commit transfers*, but this overloaded the