Seonglae ChoConsistency
Efficiency 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
Mistakes engineers make in large established codebases
What I've learned from ten years working on projects like this
https://www.seangoedecke.com/large-established-codebases/
Greppability, Searchability
Quick guide to web typography for developers · OlegWock
80/20 guide on how to make your blog posts look pretty, for free.
https://sinja.io/blog/web-typography-quick-guide
Efficiency trades off against resiliency - Made of Bugs
https://blog.nelhage.com/post/efficiency-vs-resiliency/
Every software is messy and has skeletons
You need to accept one truth - every shop is messy and every app has its skeletons. Period. Welcome to the backstage of the software world, where the
https://vadimkravcenko.com/shorts/every-app-has-its-skeletons