Egon Wuchner

Co-Founder & CEO of Cape of Good Code. Egon has a Master in Mathematics from the University of Augsburg. He worked for 18 years at Siemens. His main focus was software architecture, quality and analytics. Egon was also an internal consultant for these topics and trained international teams. Egon's focus is on product development and consulting.
Co-Founder & CEO of Cape of Good Code. Egon has a Master in Mathematics from the University of Augsburg. He worked for 18 years at Siemens. His main focus was software architecture, quality and analytics. Egon was also an internal consultant for these topics and trained international teams. Egon's focus is on product development and consulting.
Cooperation with digatus

Cape of Good Code agrees cooperation with digatus for Software Due Diligence projects

Cape of Good Code GmbH and digatus it Consulting GmbH have signed a cooperation agreement for the joint implementation of Software, Technology and IT Due Diligence projects as of 1 May 2022. The aim of the cooperation is to expand digatus’ M&A service portfolio by using the DETANGLE Analysis Suite.

The DETANGLE Analysis Suite reveals hidden risks in the source code and in the development processes and thus supports investors in making risks in the acquisition of software assets transparent at an early stage.

About digatus

digatus it consulting GmbH is an international provider of IT consulting and services based in Munich. With over 110 employees, digatus has been successful in the market for eight years. Its clients include investors and private equity funds, as well as medium-sized companies and corporations.

About Cape of Good Code

Cape of Good Code GmbH is a leading specialist for the analysis of code and architecture quality in software. Cape of Good Code counts start-ups, investors, software service providers as well as purchasing and R&D departments among its customers.

Posted by Egon Wuchner in Press About Us, 0 comments
Talk Software Quality Days 2022 – 18.05.2022

Technical debt – why the term causes more confusion than clarity. And how to do it better.

Konstantin Sokolov and Egon Wuchner give a presentation on the following topic:

Are we software engineers really clear what we mean when we talk about technical debt?

“Sure”, is the answer, “it’s about smells, bugs, need for refactoring, missing tests …”. To some extent, we can even measure their scope and need. But how do we decide what to address first? How and what do we measure so that other stakeholders even understand us and how do we convince product owners, project managers, and department heads of the necessary budget?

In the talk we show how to do it better based on data. How to start with the consequences of technical debt, capture maintenance and increasing overheads in development as KPIs and identify their hotspots in the code. How to identify code quality, architecture quality, test quality, etc. as root causes and correlate them with the KPIs. And how to forecast technical debt in the architecture in numbers in order to perform a cost-benefit analysis. And how team collaboration also impacts Technical Debt. These challenges have been the same for several decades. Microservices have not changed that.

Where an when?

Posted by Egon Wuchner in Events, 0 comments
A New Approach To Predict Burnout Risk for Software Developers

A New Approach To Predict Burnout Risk for Software Developers

September 10, 2021 by Egon Wuchner


Summary

  • Burnout symptoms are often a result of suboptimal procedures and working conditions. They are signs of a serious and protracted illness.
  • Especially, burnout of software developers is more widespread than one might suspect. It hits companies via increased employee turnover, reduced team productivity and above-average sick leave just as hard as the affected employees. 
  • Amongst many other reasons, “meaningless” work, frequently changing priorities, unrealistic goals, deadlines, and overwork are disproportionately often named as causes.
  • Early indicators for these most important burnout causes can be identified from the work on the software code with the DETANGLE Analysis Suite.
  • With these analysis results, project leaders/-management have information at hand to identify health-threatening working conditions of their developers at an early stage and can initiate countermeasures timely.   
  • By regularly applying these analyses, additional information regarding the trend of the relevant key metrics will become available. Over time it becomes increasingly easy to narrow down the causes of a developer’s burnout and to avoid it before the individual and as a consequence, the organisation is seriously impacted.

Continue reading →

Posted by Egon Wuchner in General, 0 comments
Software Due Diligence – Focus on Contributors and Their Cooperation

Software Due Diligence – Focus on Contributors and Their Cooperation

17th of May, 2021 by Egon Wuchner


Summary

  • The success of a software company takeover depends to a large extent on the retention of key developers.
  • The DETANGLE® Software Analysis Suite identifies different groups of key developers.
  • The acquisition risk decreases if the investor can conceive measures at an early stage to retain these employees.
  • The tool also analyses the entire effort and knowledge distribution in the development team. The optimisation of knowledge distribution enables quality and efficiency improvements. 
  • An optimised knowledge distribution also reduces the dependency on individual persons.

Continue reading →

Posted by Egon Wuchner in General, 0 comments