Duration: 4 working days
2 trainers per course
For 8 to 10 participants
With you or with us
1,924€ per participant
Our training is based on Clean Code expertise from over 15 years of project business. Benefit from practical experience as well as tried and tested methods and tools that can be transferred directly to everyday work.
Our Clean Code trainers were personally trained by Stefan Lieser, one of the co-founders of the Clean Code Development Initiative. In this way, we guarantee the highest quality and in-depth expertise.
We tailor the content and structure of the training specifically to your level of knowledge. In addition, you decide when, for how long, and where the training should take place. Perfectly integrated into your business process.
Our Clean Code training courses are aimed exclusively at people with programming know-how. In other words, to software developers, system and software architects, or software testers.
However, our trainers also offer presentations at management level, where they discuss the benefits of clean code development from a business perspective. Our CTO Sebastian Betzin explains how Clean Code can contribute to corporate success in the following on-demand video:
As I said, programming know-how is required to be able to follow the courses. Participants must understand programming examples in C#, Java, Typescript, etc. and also be able to write the languages.
Especially for practical exercises, all participants should have a computer with an installed development environment, such as VSCode or VisualStudio, bring along.
That depends entirely on you and your wishes. We adapt the length of our Clean Code trainings to your learning goals. These can be one-day workshops or sessions over several days.
That is also up to you. Either you come to us in Karlsruhe or our Clean Code trainers come to your company and hold in-house trainings with your team.
Just write to us via the contact formthat you're interested in Clean Code training, and we'll get back to you. If you already know when you would like to take part in the training, how many participants there will be and what learning goals you are pursuing, simply enter this information in the appropriate free text field.
Not all software quality is the same. We distinguish between internal and external quality, with our Clean Code training focusing on internal quality—that is, the quality of the source code. We address the topics of readability, comprehensibility, testability, and adaptability (evolvability).
The benefits of a shared quality mindset:
The Clean Code Development Initiative is based on the book Clean Code by Robert C. Martin. Building on this, two German developers, Stefan Lieser and Ralf Westphal, conceived a standard-setting value system for software developers in 2009, which includes learning modules as well as a collection of principles and practices. At the very top are the four Clean Code values:
Flow Design is a technique for planning and structuring source code meaningfully before it is even written. It always addresses the question of how to get from a requirement to the actual code. The technique works by hierarchically breaking down requirements into their smallest units: data flows.
The benefits of Flow Design:
Automated tests not only ensure that source code works correctly, they are also an effective way to better understand and define requirements. They also provide developers with confidence and security. However, writing tests and complex test suites—consisting of system, integration, and unit tests—is a craft in itself. Our trainers teach fundamental concepts, techniques, and the necessary technologies, such as SonarCloud, to increase test coverage in the back and frontend and achieve high ratings in penetration tests.
While all Clean Code principles have their place and importance, there are some that should essentially always be applied and are therefore a key part of our training:
Dependencies in source code can help simplify structures. However, too many dependencies can lead to code changes having unexpected side effects, causing the code to become cluttered over time. In our training sessions, we provide participants with techniques and best practices to effectively manage and, if necessary, resolve dependencies.
Pair programming, or tandem programming, describes a Clean Code development method where two developers work on the same problem and the same code simultaneously. While this approach is very useful in some cases, it can be inefficient in others. Our trainers provide best practices on how and when this method makes sense.
Clean Code Development must not become an end in itself. When working with source code, you will always find areas that can be optimized. But at some point, this is no longer productive and is no longer cost-effective. The only question is: when?
In our Clean Code training sessions, we provide participants with the tools to arrive at the right Definition of Done – individually tailored to the project, the requirements, and the company's goals.
The right mindset is just as important as the technical craft. It is about consistently upholding and advocating for Clean Code values. Consequently, these topics are not taught in a single isolated session, but are integrated throughout the entire training. Specifically, this covers agile working, efficiency through focus, reflection, accountability, expectations, and collaboration.
You only learn Clean Code by doing. That is why we place great importance on a high practical component in our training sessions. This includes small exercises to deepen understanding of a topic discussed in theory, as well as collaborative code reviews where the results of these exercises or other code examples are discussed in detail with all participants.
Code checks of an existing application are a great way to find out where a team stands with its codebase. Similar to a code review, the code is analyzed by our trainers together with the original developers. Through this reflective approach, participants learn a great deal about themselves and their own working methods.
