If you break the CQS...
Potential problems:
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🔹" title="Kleine blaue Raute" aria-label="Emoji: Kleine blaue Raute">Unclear whether functions have side effects.
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🔹" title="Kleine blaue Raute" aria-label="Emoji: Kleine blaue Raute">Function names are often deceiving: functions do more than they say.
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🔹" title="Kleine blaue Raute" aria-label="Emoji: Kleine blaue Raute">Violations of Single Responsibility Principle.
https://abs.twimg.com/emoji/v2/... draggable="false" alt="🔹" title="Kleine blaue Raute" aria-label="Emoji: Kleine blaue Raute">Temporal couplings: the order in which you call functions with side effects matters. 2/3
Example: popping the top element of a stack. The "pop" function removes one element and returns it. Therefore, it modifies the state of the stack and returns a value. 3/3