Unsolicited code advice because this isn't a sufficiently widespread practice: Long files of source code (>500 lines) are the equivalent of that drawer in your kitchen or shop that has a bit of everything, and are an unprofessional way to share a work environment with others (or yourself). Maintain your source code's ontology with small files and directory structure. This looks different in every language but each file should be just one concept with exceptions only for "supporting concepts."
Conversation
Notices
-
Embed this notice
jbr (jbr@mastodon.social)'s status on Friday, 09-Jun-2023 06:49:58 JST jbr
-
Embed this notice
jbr (jbr@mastodon.social)'s status on Friday, 09-Jun-2023 06:49:58 JST jbr
There aren't that many things that rails got right, but the systematic application of conceptual ontology to source code is high up there. One file, one thing. Organized by type of thing, recursively.
-
Embed this notice
jbr (jbr@mastodon.social)'s status on Friday, 09-Jun-2023 06:49:58 JST jbr
and why is it always the most senior engineers who write the longest files
-
Embed this notice