CQSE Blog
News & Updates
All news and updates
Categories
Dr. Tobias Röhm
2016
Man vs. Tool? On the Role of Software Tools and Human Experts in Software Quality Activities
In a recent software quality audit, our static analysis tool Teamscale found that the comment ...
Martin Pöhlmann
2016
Lessons from code reviews in the wild (part 2): Get rid of unnecessary code
One side-effect that I have observed from performing code reviews for years is that the code after ...
Dr. Corneliu Popeea
2016
Static Analysis to Inspect Third-Party Library Usage
At CQSE, we use Teamscale and static analysis for assessment of technology suitability: Get ...
To Blacklist or Not to Blacklist
Analysis tools for your source code, like Teamscale and others, produce a list of findings—or ...
Rainer Niedermayr
2016
Why we don’t use the Software Maintainability Index
The Software Maintainability Index (MI) is a single-value indicator for the maintainability of a ...
Fabian Streitel
2016
»I'll clean up later«—Tasks in Teamscale
Anyone writing code knows that famous sentence: »I’ll clean that up later«. We have all heard it. ...
Thomas Kinnen
2016
A new language will not fix your maintainability issues!
Have you ever run into a »new« or »trending« programming language (Rust, nim, Kotlin, etc.), ...
Dr. Elmar Jürgens
2015
What can Clone Detection across System Boundaries Reveal about Architectural or Organizational Problems?
Teams, not individuals, build most software systems. The organization of these teams thus strongly ...
Dr. Benjamin Hummel
2015
Save the Semicolon
These days, it seems that a modern programming language is required to not use semicolons at all, ...
Like our blog?
We write about many software-quality topics.
Our Team
Dr. Tobias Röhm
2016
Man vs. Tool? On the Role of Software Tools and Human Experts in Software Quality Activities
In a recent software quality audit, our static analysis tool Teamscale found that the comment...
Martin Pöhlmann
2016
Lessons from code reviews in the wild (part 2): Get rid of unnecessary code
One side-effect that I have observed from performing code reviews for years is that the code after...
To Blacklist or Not to Blacklist
Analysis tools for your source code, like Teamscale and others, produce a list of findings—or...
Rainer Niedermayr
2016
Why we don’t use the Software Maintainability Index
The Software Maintainability Index (MI) is a single-value indicator for the maintainability of a...
Fabian Streitel
2016
»I'll clean up later«—Tasks in Teamscale
Anyone writing code knows that famous sentence: »I’ll clean that up later«. We have all heard it....
Dr. Benjamin Hummel
2015
Save the Semicolon
These days, it seems that a modern programming language is required to not use semicolons at all,...
CQSE Blog
Dr. Tobias Röhm
2016
Man vs. Tool? On the Role of Software Tools and Human Experts in Software Quality Activities
In a recent software quality audit, our static analysis tool Teamscale found that the comment...
Martin Pöhlmann
2016
Lessons from code reviews in the wild (part 2): Get rid of unnecessary code
One side-effect that I have observed from performing code reviews for years is that the code after...
To Blacklist or Not to Blacklist
Analysis tools for your source code, like Teamscale and others, produce a list of findings—or...
Rainer Niedermayr
2016
Why we don’t use the Software Maintainability Index
The Software Maintainability Index (MI) is a single-value indicator for the maintainability of a...
Fabian Streitel
2016
»I'll clean up later«—Tasks in Teamscale
Anyone writing code knows that famous sentence: »I’ll clean that up later«. We have all heard it....
Dr. Benjamin Hummel
2015
Save the Semicolon
These days, it seems that a modern programming language is required to not use semicolons at all,...