Becoming a clean code trainer Clean code has become an increasingly important topic in software development in recent years. While the idea of clean code was initially discussed critically, its necessity is now generally recognized. In individual cases, there may be reasons to write software,
Software design - With Flow Design to Clean Code No Big Design Upfront software systems are quite complex these days. Simply programming away during development quickly leads to problems: you no longer understand your own code. Only code that has been created according to the Clean Code Developer principles enables developers to understand their own code.
[amazon fields="0132350882″ image_size=large value="thumb"] If you're a software developer, you've probably heard of clean code. In today's fast-paced world, it's important for companies to work quickly and efficiently. However, this can sometimes lead to the quality of the source code being neglected. A clean code workshop can
Error-free software? A pipe dream! Automated tests are standard and yet in practice there is still a lot of catching up to do when it comes to testing. Is "defensive programming" therefore an additional building block that needs to be followed? Yes and no. When we question in our training sessions whether the parameter check at the beginning of each method
A multi-tenant solution From now on, all participants in our training courses will receive a badge in Open Badges format. For a long time now, a certificate of attendance has been issued at the end of the course. We have developed our own application that generates a PDF for each participant and sends it by email. This solution is precisely tailored to our needs.
The IOSP is one of the most important principles for structuring code. IOSP stands for Integration Operation Segregation Principle. This means that methods can be divided into two categories: Integration vs. Operation. The rules are very simple: Integration May only call own methods Operation May only call external methods
Clean code is not an end in itself. And not a dogma, as I have already stated elsewhere. The Clean Code Developer principles and practices serve to achieve values. In coding, these are primarily the values of changeability and correctness. The value of production efficiency is often also affected. In order to achieve a differentiated
You may ask yourself from time to time why you are actually working in a "team"! Everyone is working on the same software, but somehow it's every man for himself. Everyone builds their part of the system, now and again with support or perhaps in pairs. Structures grow organically with everyone
Clean Code The term Clean Code was coined by Bob C. Martin and his book of the same name. Shortly after its publication, Ralf Westphal and I founded the Clean Code Developer Initiative and compiled 45 principles and practices. Clean Code, the book, was a stimulus for us to get to grips with
Update 14.02.2024: This article has been slightly revised. About the short-sighted decision to develop quickly instead of cleanly. Anyone who studies the principles and practices of the Clean Code Developer Initiative will realize that it takes time to apply all the building blocks. There are building blocks that can quickly help a developer to achieve good
CCD Academy GmbH
Am Steinernen Kreuz 27
53343 Wachtberg
English 
German