From the list at the link, I would argue that the following are mostly orthogonal of, and certainly not requirements from, clean code: 1. Performant 2. Safe

From the list at the link, I would argue that the following are mostly orthogonal of, and certainly not requirements from, clean code: 1. Performant 2. Safe 3. Scaleable 4. Easy to delete --- Performant: I can write you a nice clean bubble sort implementation, which will obviously not be performant. Safe: You could write a nice clean server which reads input from a network socket and executes it via `system(...)`. This would not be safe. Scaleable: That's not even properly defined. How would you "scale" my device driver? Or my microcontroller logic? ... does that mean those can never be clean? Easy to delete: To delete and replace? To delete for building tests for other parts of the code? Didn't even get that.