6 links tagged with all of: code-quality + maintainability
Click any tag below to further narrow down your results
Links
This article analyzes the quality, security, and maintainability of code generated by leading AI models like GPT-5.2 High and Gemini 3 Pro using SonarQube. It presents findings on functional performance, complexity, concurrency issues, and security vulnerabilities across various models.
This article presents a leaderboard ranking various LLMs based on their performance in code quality, security, and maintainability. The analysis evaluates 4,444 Java programming assignments, providing metrics like pass rates and issue density for each model. Key insights include the top-performing models and their specific strengths.
Ugly code can hold hidden value, particularly when it reflects deep knowledge of a problem domain. Often, it contains insights that aren't documented elsewhere and can be more helpful than starting from scratch. Working with legacy code may be challenging, but it can reveal lessons that aren't immediately clear.
The article discusses the emergence and persistence of disposable code in software development, highlighting its advantages and challenges. It emphasizes how disposable code can lead to faster iteration and innovation but also raises concerns about code quality and maintainability. The piece advocates for a balanced approach to incorporating disposable code into programming practices.
The article discusses the importance of leveraging a type system in programming to enhance code quality and maintainability. It emphasizes how a well-structured type system can prevent errors and improve developer efficiency by providing clear documentation and better tooling support. Practical examples and benefits of using a type system are highlighted to encourage adoption among programmers.
The article emphasizes the importance of avoiding abstract code in programming, advocating for clarity and simplicity in code design. It suggests that clear, straightforward code enhances maintainability and collaboration among developers. The author argues that overly abstract code can lead to confusion and hinder the understanding of the underlying logic.