Skip to main content

Naming Features

Giving good names to features can help to improve the quality and reliability of the application, and make it easier for teams to work together and make decisions about features.

When naming features take into account:

  • Be descriptive and clear: Feature names should clearly and accurately describe what the feature does. Avoid using internal jargon or abbreviations that might not make sense to someone who is not familiar with the project.

  • Use consistent naming conventions: Adopt a consistent naming convention and stick to it. This makes it easier to find and manage features in the future. For example, you could use camelCase, snake_case, or PascalCase.

  • Avoid too long names: Feature names should be short, concise and easy to read. Long names can make it harder to quickly understand what a feature does.