CQS programming principle
The CQS (Command-query Separation) programming principle assumes that each function in the project can only execute a command (any active action) or only a data retrieval query.
For example, your project has a function that highlights the input, but it should not simultaneously parse the information entered by the user and send it to the database; another function is needed for this.
See also
-
principle
SOLID,
which sets guidelines for OOP-based software -
principle
DRY,
which is the division of software into small components -
principle
KISS,
which involves abandoning the complication of software -
principle
YAGNI,
which involves the rejection of redundant software functionality -
principle
LoD,
which is used in software development -
responsibility separation principle,
which is used in software development