InfoQ Homepage Code Quality Content on InfoQ
-
How to Sustain Quality and Velocity in a JavaScript or TypeScript Project?
The JavaScript language and its ever-changing ecosystem of packages and practices can make codebases quickly become hard to maintain. The resulting loss of development velocity and/or code quality can be prevented without rewriting everything from scratch, nor pausing the development of new features. In this article, we have analyzed a few best practices to help avoid that.
-
The Importance of Pipeline Quality Gates and How to Implement Them
A quality gate is an enforced measure built into your pipeline that the software needs to meet before it can proceed. This article covers how to get the maximum benefit from quality gates. Making good use of quality gates not only can improve the quality of your software, but it can also improve your delivery speed.
-
Evolving DevOps to Enable Quality at Speed Software
DevOps must evolve to include Quality at Speed to address issues with delivering timely business value and innovation, siloed teams lacking alignment, a fragmented toolchain, and quality sacrifices. Infrastructure, Developer and Experimentation platforms are the three fundamental platforms enabling Quality at Speed software delivery
-
Code Red: the Business Impact of Code Quality
Everyone in the software industry “knows” that code quality is important, yet we never had any data or numbers to prove it. In this article, we explore the impact by diving into recent research on code quality. With twice the development speed, 15 times fewer bugs, and a significant reduction of uncertainty in completion times, the business advantage of code quality is unmistakably clear.
-
Talking Like a Suit - Communicating the Importance of Engineering Work in Business Terms
This article explores how to construct engineering work as a story, including clearly presenting a problem, offering a solution, and showing the business a path to success that solves their problem and avoids failure. By presenting your case in this way, you significantly increase your chances of getting these engineering problems addressed, while also becoming a better partner for the business.
-
Technical Debt Isn't Technical: What Companies Can Do to Reduce Technical Debt
In this article, three experts discuss some of the key findings of the “State of Technical Debt 2021” report including the impact of technical debt on engineering teams, the pros and cons of dealing with maintenance work continuously, the future of technical debt and what each engineering teams can do to communicate the importance of dealing with technical debt to companies’ leadership.
-
Improving Testability: Removing Anti-Patterns through Joint Conversations
Code is always testable, but the cost may be high, and the effort exhausting. We can change code to be highly testable by identifying anti-patterns and fixing them. And developers can make the code fit the test requirements, by having discussions with the testers who actually test it.
-
Easy Guide to Remote Pair Programming
Remote pair programming can be an extremely powerful tool, it's a form of social programming. When pairing remote, you need a lot more setup and more tooling in place, so that the two team members can work together effectively. With remote pair programming quality communication is essential because we lack the physical presence that gives us so much non-verbal communication.
-
Signs You’re in a Death Spiral (and How to Turn It around before It’s Too Late)
Don’t let feature work blind you. Enterprises are ramping up their software delivery to compete in the digital-first world. But more features and faster time-to-market can lead your business into a death spiral if you neglect technical debt and risk work. Learn how to use value stream metrics to identify whether your business is in danger and how to reverse the trajectory before it’s too late.
-
In the Search of Code Quality
Software development process being a convoluted interplay of technical, business, sociological and psychological forces makes it very hard to understand. This leads to a multitude of myths and hypes. Recent scientific research challenges many commonly held beliefs and intuitions.
-
Q&A on the Book Refactoring - Second Edition
The book Refactoring - Second Edition by Martin Fowler explores how you can improve the design and quality of your code in small steps, without changing external behavior. It consists of around seventy detailed descriptions of refactorings, including a motivation for doing them, the mechanics, and an example.
-
How to Slow Down to Go Faster Than Ever in Software Development
Going fast without control could be the biggest enemy of software development. By slowing down on people, we improve professionalism and craftsmanship. By slowing down on process, we improve adaptation and efficiency. And by slowing down on product, we improve automation and quality. When we focus on these areas, we start to cultivate a development culture enabling software development fast.