As a developer I find I'm paid very little for lines of code. I'm paid primarily for making decisions and for recording those decisions clearly. Application so

As a developer I find I'm paid very little for lines of code. I'm paid primarily for making decisions and for recording those decisions clearly. Application source code is one way those decisions are recorded. Call graphs, data flow graphs, help text, application documentation, API documents, troubleshooting guides, monitoring code around production applications, tests, configuration and build management files, and commit messages are others. Given that point of view, here's my advice.: Make the source and the other artifacts as simple as possible, but no simpler. Cross-reference where it helps most, but not excessively. Compose things from modular pieces rather than building monoliths when you can. Document the parts and the whole.