Readable code

← Back to concept

Predictable conventions

Use descriptive snake_case names where the project follows that convention. Type names use a T prefix. Prefer explicit type contracts and as const mappings. Keep related code close to its owner and follow existing conventions before introducing a new pattern.

type TProgram = { id: string, title: string }
const visible_programs = programs.filter(program => program.title.length > 0)

Use early returns for conditions and typed registries for genuine mappings. Keep imports grouped by external packages, layers and relative paths. Avoid reformatting unrelated code.

A readable expression around 130 characters can stay on one line. File length is a reason to inspect responsibilities, not to compress the code mechanically. Comments explain a decision or an invariant rather than repeat the implementation.