one thing i’d add that works well in javascript that is similar to “eye level is buy level”

and that is “hoist the system”

the important things that any file does is at the top.

the things those things depend on are either imported from packages at the top of the file or hoisted from functions below.

the things those functions depend on are hoisted from below them and so on

this makes every file in a system easy to grok because the first things are the business needs and as you scroll down, you get into the weeds and the implementation details— important things, but conversationally irrelevant things— this paradigm makes cross functional collaboration more effective as it drives engineers to understand business context with literal forcing functions.