This page lists past articles from the weekly series "Improving code quality".
At LY Corporation's development organization, we focus on improving code quality and development culture to maintain high development productivity. One of our various initiatives is the Review Committee's activities. This involves re-reviewing merged code and providing feedback to reviewers and authors. The insights gathered from these reviews are shared internally every week through a weekly report.
Some topics shared in this weekly report are specific to languages like Kotlin or Swift, or limited to platforms like Android or iOS. However, many articles cover topics that can be applied to programming in general, regardless of language or platform. We select such generally applicable articles and present them on the blog as the "Improving code quality" series. (Note that the code used for explanations in the articles is often in Kotlin.)
(Last updated: 2024-11-18)
- Session 23: Too early to return
- Session 22: To equal, or not to equal
- Session 21: Knock on the constructor for good luck
- Session 20: Exceptional exception overwrapping
- Session 19: Child safety lock
- Session 18: Missing the forest for the trees
- Session 17: A castle built on sand
- Session 16: Where there is null, there is smoke
- Session 15: Grammar represents names
- Session 14: The only responsibility of assigning responsibility
- Session 13: Clone family
- Session 12: Set discount
- Session 11: Even functions get tired of calls
- Session 10: Be mindful of keeping a proper distance
- Session 9: Retrace your steps
- Session 8: Reality and illusion
- Session 7: A seat for a new member
- Session 6: If I had eight hours to chop down a line...
- Session 5: Bad enumerations drive out good layers
- Session 4: Testing with breaking a door
- Session 3: Strategy without a strategy
- Session 2: Have you double-checked your code?
- Session 1: Don't cry over spilt errors