AI Briefing#code-quality
The latest AI and developer news about #code-quality, with the original source and a short summary.
The latest AI and developer news about #code-quality, with the original source and a short summary.
When defining the relationship between UI elements and state values, splitting code by UI element is more advantageous in terms of readability and stability.
It presents a design method to prevent invalid state creation caused by value duplication when applying aggregation or composition after separating data models.
This analyzes the problems that arise when sharing object instances to share logic, and presents a way to design by distinguishing between type dependency and object dependency.
Factory functions that use generic arguments undermine the flexibility and robustness of code, so parsing responsibility should be separated for each object.
Setting a value with special meaning as a default parameter can cause bugs through unintended object creation.
This article introduces the LLM-based automated unit test generation and compile, execution, and coverage verification process through a case study of Kakao's test generation agent.
This proposes a design approach that keeps function names and behavior consistent, in order to prevent bugs caused by mismatches between a function's name and its actual behavior.
This presents a design approach to prevent the problem that arises when using null as the termination signal for an Iterator, since it cannot be distinguished from actual data.
This analyzes how attempts to prevent domain model anemia can lead to circular dependencies and design flaws.
When splitting a function apart, you should gather the logic that determines the final return value in one place rather than scattering it, to make maintenance easier.
It proposes a method of resolving missing mapping issues that can occur when adding an Enum type through static verification instead of tests.
To resolve the 'split knowledge' problem caused by a function depending on a specific data format, this proposes a refactoring approach that moves domain knowledge to the call site.
It suggests explicitly defining task order by leveraging function arguments and return values, thereby increasing cohesion and reducing coupling.
This explains how to improve code stability by consolidating related data scattered across multiple Maps or Lists into a single data class.
This analyzes state management errors and design flaws that arise when the lifecycles of objects become entangled with each other.
The 11st search frontend redesigned its structure around minimal units of responsibility and explicit rules.
Kakaopay introduces how it manages code quality and security in a DevSecOps environment using Sonarqube.
This article introduces a case study from Oliveyoung's Product Squad, where detekt, reviewdog, and GitHub Actions were adopted to automate code conventions and improve code quality.
Kurly's Logistics Development Team improved code quality and leveled up team members' understanding of the project through refactoring the inbound management system.
A new hire on the LDD team removed over 500 code convention violations using terminal commands and helped establish a code review culture within the team.
This guide introduces how to write Shareable Configs for sharing ESLint settings via npm and the process of developing AST-based custom rules.