Content:

Clean and efficient code enables continuous adaptation of software to new needs. Most developers fundamentally know how clean code should look like but often lack the knowledge of how to specifically and systematically detect and improve poor code.

The workshop includes the following topics:

– Introduction to Clean Code
... - Why is Clean Code important?
... - How not to fall into the perfectionism trap
... - The economics of clean code

– Effective Naming and Abstraction
... - The art of naming variables, methods, and classes
... - Finding meaningful and precise names
... - Identifying the right level of abstraction

– Clean Code Principles
... - SOLID principles to improve code structure
... - DRY (Don't Repeat Yourself) vs. WET (Write Everything Twice)
... - KISS (Keep It Simple, Stupid) and YAGNI (You Aren't Gonna Need It)
... - Composition over Inheritance
... - Integration Operation Segregation Principle (IOSP)
... - Law of Demeter

– Recognizing and Naming Code Smells
... - Identifying common anti-patterns
... - Long Methods, Large Classes, Feature Envy
... - Primitive Obsession and Data Clumps
... - Shotgun Surgery and Divergent Change

– Refactoring Strategies and Tactics
... - How to improve existing code without changing its functionality
... - Using automated refactorings in the IDE
... - Boy Scout Rule and continuous improvement
... - Safe refactoring techniques

– Testing & Code Quality
... - Unit testing principles
... - Meaningful tests vs. mere coverage
... - Test Driven Development (TDD) basics
... - Using mocks and fakes effectively

– Design Patterns
... - Key design patterns and when to use them
... - Avoiding over-engineering
... - Practical application of selected patterns

– Error Handling and Resilience
... - Exception handling strategies
... - Fail-fast principle
... - Robust error handling

– Modularization and Architecture
... - Project structure and dependency management
... - Separation of Concerns
... - Clean Architecture basics
... - Ports & Adapters

– Working with Legacy Code
... - Characterization tests for existing code
... - Strangler pattern for gradual migration
... - Code Archaeology

– Code Reviews and Team Practices
... - Best practices for effective code reviews
... - Giving and receiving constructive feedback
... - Establishing continuous improvement

You will not only get to know these concepts but also apply them practically.

Disclaimer: The actual course content may vary from the above, depending on the trainer, implementation, duration and constellation of participants.

Whether we call it training, course, workshop or seminar, we want to pick up participants at their point and equip them with the necessary practical knowledge so that they can apply the technology directly after the training and deepen it independently.