Too many pipe commands cause inefficiency

Software ResiliencyProgramming Best Practices

Why you should care

Having too many pipe commands could result in code inefficiency as well as possible entry of bugs and crashes in the code due to increased stringing and redirections as a result.

Business Impacts

Using pipes in a program can be a risky decision as it tends to be wasteful in both time and productivity. Using more pipes will further decrease productivity as well.

Production Risk

How we detect

This code insight shows that while piping commands are useful, they should be avoided if too many of them exist.


About CAST and Highlight’s Code Insights

Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.

See featuresHow it works