"Convention over Configuration," often abbreviated as "CoC," is a principle in software development that suggests that in a software framework or development environment, default configurations and conventions should be preferred over explicit configurations. In other words, if developers adhere to certain naming conventions and structures, they should be able to develop their software without extensive configuration.

The "Convention over Configuration" principle has several advantages:

1. Simplified Development: Developers need to worry less about configuring software components. Instead, they simply follow the established conventions, making development faster and smoother.

2. Consistency: Since all developers on the team use the same conventions, this leads to a more consistent codebase, which facilitates collaboration and maintenance.

3. Avoiding Redundancy: Conventions can help avoid redundancy in configuration. Instead of having to configure specific settings for each part of the application, developers can rely on default configurations.

4. Clarity: Adhering to conventions makes the code more understandable for developers, as they know where to find specific parts of the application or configuration.

A well-known example of "Convention over Configuration" can be found in the Ruby on Rails framework, which uses default naming conventions for database tables, models, controllers, and views. By following these conventions, a developer can build a database-backed web application without manually configuring database tables or routes.