In our knowledge area we have prepared blog articles, wiki articles and case studies on the topic of software for you.
Large and small targets, or young and established software companies, require different areas of investigation and approaches to software due...
Software is often a key value driver in transactions. Thorough software due diligence not only reveals risks, but also identifies opportunities. What...
What is software modernization about? How does it differ from software quality assurance? Learn more in our wiki article!
The number one pitfall in developer stack ranking is to evaluate purely competitively and ignore collaboration. And secondly ...
Pitfall number two when stack ranking: neglecting software quality!
Git squash merge doesn't really help to produce clean commit histories. It's just a crutch to hide the inability to split commits in a reasonable...
Contribution or knowledge balances have demonstrably positive effects: fewer bugs and less maintenance effort. Bidirectional collaborations pay off!
Developer productivity and team alignment are not mutually exclusive. It depends on the right mix of individual and team contributions from...
Team productivity trumps developer productivity. On the other hand, we give in to the team illusion. The real controversy is how to achieve team...
Cape of Good Code can determine an unhealthy level of stress in software projects and which developers might be most affected.
In order to conclude better contracts for better software when purchasing customised software, a rethink and new tools are needed in purchasing.
Cape of Good Code certifies the Vaadin Flow Web Framework as having good architectural quality after measurable improvement efforts in the previous...
What is Software Due Diligence? And why it gets more and more relevant. Learn more in our wiki article!
Using a modified PDCA cycle, we look at what software procurement can and should do in the context of continuous supplier analysis.
Volatile product specifications in procurement require that code architecture remains future-proof. New acceptance criteria and quality metrics are...
Cape of Good Code's software analyses provide data-based help in allocating the ever-scarce development resources in software engineering
Developer burnout is more widespread than you might think. With DETANGLE® you can automatically detect early indicators of burnout from the work on...
White Stripes on the Tail Put Maschine Guns of a Fighter Plane Out of Action - A Technical Debt Story
How cognitive biases make us overlook problems in our code and how we vigorously defend our opinions against data-based insights. And what can help...
Cape of Good Code identifies different groups of key developers and the overall distribution of effort and knowledge within a Sofware Due Diligence.
Identifying risky hotspots must consider more than code quality and change rates. It's all about the architecture!
10 rules & best practices your supplier should absolutely follow if they want to be listed as a stress-free supplier to their customers.
Data-based analysis shows that Collective Code Ownership can do harm and affected code areas can probably become hotspots of maintenance.
Despite good SonarQube code quality metrics for the Corona-Warn-App, there are noticeable findings based on DETANGLE® that contradict this good...
Fields of investigation such as technical debt, architecture, documentation, knowledge distribution and development processes must be analyzed using...
Software targets have special valuation risks. A software due diligence is therefore a prerequisite for evaluating these technological risks.
Structural dependency analyses are of limited value in identifying architectural hotspots. There are more precise alternatives.
Pitfalls of agile remote development and countermeasures for effective collaboration in geographically distributed teams.
Practical guide on how to improve software quality and establish effective monitoring through the right selection of issue types.