Seonglae ChoEfficiency trades off against resiliency
Reachability ⇒ Performance ⇒ Scalability ⇒ Reusability ⇒ Readability
훈수가 더 깐깐하다 보니, 코드 퀄리티를 위해서 훈수는 꼭 필요하다 Code Review 하지만 그러기 위해서 팀장은 훈수둘 실력이 있어야함
Code that is working for the wrong reasons is code that is going to break when you least expect it.
- test code coverage Test Code Coverage
- performance score (i.e. lighthouse score) Software Performance
- formatter, linter warnings Coding Convention
- no repeat
- consistent code for readability
- tell typed and comment or document generating
Code Quality Usages
