AI relatedhere, a piece of code I wrote the other day where I reference further down functions (L86 referencing L161)
in this case for the utterly simple reason of: the auxiliary Composable was added after the main one.
and even if that wasn't the case, I tend keep the main node of a file on top and any auxiliary or utility nodes on the bottom, to avoid cluttering with stuff that most of the time I won't need to read/change (weirdly enough, constants I do keep above though)
coding; AI related@kitten yeah of course … won't anyone do that?!
When writing API backend atuff at work, routes go on top (with a constant for the path prefix even above that), then route handlers and request/response structs (for de-/serialisation), then database and main logic helpers, and most other stuff (random little helper thingies, intermediate type conversion, etc.) below … only followed by the mod/block for tests.
1❤️1
1