Java Clean Code Kurs

Der Java Grundkurs wurde für 3 Tage konzipiert. Innerhalb dieser drei intensiven Tage vermitteln wir Ihnen ausnahmslos alles, was Sie als Java Einsteiger benötigen. Das spart Zeit und damit bares Geld. Für jedes Thema gibt es Beispiele und Programmieraufgaben. Die Theorie Anteil beträgt  20% und die Praxisanteil von 80%. Es gibt über 14 kleine Workshops und am dritten Tag ein Abschluss-Projekt  Folgende Themen lernen Sie in unserem Java Grundkurs für Anfänger 

Clean Code Tag 1

Code Rote

• The Company killed by Code
• Productivity Problem
• Manager Reaction
• Code Rote: Rigidity
• Code Rote: Fragility
• Code Rote: Inseparability
• Code Rote: Opacity

Clean Code

• Clean Code after Grady Boosch
• Clean Code after Bjarne Stroustrup
• Clean Code after Ward Cunningham
• Clean Code after Michael Feathers

Name Rules

• What is a good name?
• What is a bad name?
• Ottinger’s Rules for good names
• Intention-Revealing Names
• Pronounceable Names
• Searchable Names
• Describe the Problem not the Implementation
• Avoid Disinformation
• Make Meaningful Distinctions
• Avoid Encodings like Hungarian Notation
• Choose Parts of Speech Well
• Use Scope Length Rules

Function Rules

• What is a function?
• Function Grammars
• Big Function
• Extract till you drop
• Step-Down Rule
• Function Type Rules
• Command-Query Separation Rule
• Command-Query Separation Rule in Threads
• Tell, Don’t Ask Principle
• Train Wrecks
• The Law of Demeter
• Parameter List Rules
• Use Maximal three Arguments
• No Output Argument Rule
• No Boolean Argument Rule
• No null Argument Rule
• Statement Block Rules
• Do One Thing Rule
• One Level of Abstraction Rule
• Small Function Rule
• Big Functions hide Classes Rule
• Minimize Side-Effects
• Avoid and Minimize Swicth Statement

Error Handling Rules

• What is Exception and Error Handing?
• Error Handling First Rule
• Prefer Exception over special Values
• Use the most suitable Exception Classes
• Use Unchecked Exceptions (RuntimeException

Good Comments

• Good Comments
• Legal Comments
• Informative Comments
• Explanation of Intent
• Clarification
• Warning of Consequences
• TODO Comments
• Amplification
• Javadocs in Public APIs

Bad Comments

• Mumbling
• Redundant Comments
• Misleading Comments
• Mandated Comments
• Journal Comments
• Noise Comments
• Scary Noise

Clean Code Tag 2

Object-Oriented Programming

• What is Object-Oriented Programming?
• Dependency Management in OOP
• Dependency Inversion
• Switch Statement and OOP
• Switch Statement and the Fan-Out Problem

Solid Principles

• Single Responsibility Principle
• Open/Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Inversion Principle

Boundries

• The Main Area
• Learning Boundries
• Clean Boundaries

Unit Test

• Introduction to JUnit 5
• Test Life Cycle
• Junit 5 Annotations
• Junit 5 Assertion Methods

Test-Driven Development TDD

• What is Test-Driven Development TDD?
• RED Phase
• GREEN Phase
• REFACTORING Phase

Imortant Refactoring Patterns

• Rename Pattern
• Move-to Pattern
• Extract Method Pattern
• Extract Class from a Big Method Pattern
• Extract an Interface Pattern

Clean Code Tag 3

Code Smells: Names

• Choose Descriptive Names
• Choose Names at the Appropriate Level of Abstraction
• Use Standard Nomenclature Where Possible
• Unambiguous Names
• Use Long Names for Long Scope
• Avoid Encodings
• Name Should Describe Side-Effects

Code Smells: Functions

• Too Many Arguments
• Output Arguments
• Flag Arguments
• Dead Function

Code Smells: Comments

• Inapproprate Information
• Obsolete Comment
• Redundant Comment
• Poorly Written Comment
• Commented-Out Code

Code Smells: Test

• Insufficient Tests
• Use a Coverage Tool
• Don’t Skip Trivial Tests
• Test Ambiguity
• Test Boundary Conditions
• Exhaustively Test Near Bugs
• Patterns of Failure Are Revealing
• Test Coverage Patterns Can Be Revealing
• Tests Should Be Fast