> You're right of course: that's a one-time cost. I disagree. This presumes that there's some initial "onboarding" process, and that once that's done you just

> You're right of course: that's a one-time cost. I disagree. This presumes that there's some initial "onboarding" process, and that once that's done you just now will know the structure of the app for all future, never spending more effort on it. That's only true for trivial apps. What actually happens in bigger codebases is after you stop working in some section of the code for a few weeks, it falls back out of your head and you have to figure it out again. Additionally, without conventions other members of your team are constantly inventing new structures and connections between things. So really this lack of consistent organization is a continuous drag, not a one time cost.