* Available for private training only. Even bad code can function. But if code isn't clean, it can bring a development organisation to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way!
In this three-day Clean Code Workshop you will learn the principles and practices of Clean Code as described in Robert C. Martin's book: Clean Code: A Handbook of Agile Software Craftsmanship. You will also receive this book as part of the course materials.
This Clean Code workshop alternates between lectures and exercises so that you can experience, first-hand, the practices and disciplines of the following fundamental topics:
- Professionalism, Craftsmanship, and Clean Code.
- Choosing Meaningful Names
- Writing Clean Functions
- The Proper Use of Comments
- Coding Style and Formatting
- Object Oriented Programming vs. Procedural Programming.
- Error Handling Boundaries between Subsystems
- Unit testing, and Test Driven Development
- Writing Clean Classes Systems
- Plan vs. Emergence
- Smells and Heuristics.
Learn how to:
- Develop an attitude of professional craftsmanship
- Write great code and transform weak, old code
Create good names, functions, objects & classes
Format code for maximum readability
Implement complete error handling without obscuring code logic
Apply effective unit testing and refactoring techniques.
What the community says
"Very well taught. Knows his stuff."Matthew, Lead X on 3rd Oct 2018
"Enjoyed the course a lot. Thanks!"James, Capegemini on 3rd Oct 2018
"Great speaker. Good tone and delivery."Attendee on 3rd Oct 2018
"Amazing tutor, friendly, interesting. Excellent examples and explanations provided. Always willing to answer questions and give advice."Isabelle Laking, Investec
"Very interactive and charismatic instructor. Kept us very focused."Attendee
- There Will Be Code
- Bad Code
- The Total Cost of Owning a Mess
- The Grand Redesign in the Sky
- What is Clean Code?
- A review of expert opinions.
- Schools of Thought
- The Boy Scout Rule
- Use Intention Revealing Names
- Avoid Disinformation
- Make Meaningful Distinctions
- Use Pronounceable Names
- Use Searchable Names
- Avoid Encodings
- Avoid Mental Mapping
- Class Names
- Method Names
- Don't be Cute
- One Word per Concept
- No Puns
- Solution Domain Names
- Problem Domain Names
- Do One Thing.
- One Level of Abstraction
- Switch Statements
- Function Names (again).
- Arguments and Parameters
- Side Effects
- Command Query Separation
- DRY - Don't Repeat Yourself.
- Structured Programming
- Why and When to Write Comments
- Explain Yourself in Code
- Good Comments
- Bad Comments
- The Purpose of Formatting
- Vertical Formatting
- The Newspaper Metaphor
- Horizontal Formatting
Objects and Data Structures
- Data Abstraction
- Data/Object Anti-symmetry
- The Law of Demeter
- Data Transfer Objects
- Use Exceptions not Return Codes
- Write your try/catch Statements First
- Use Unchecked Exceptions
- Provide Context with Exceptions
- Define Exception Classes for Callers
- Define Normal Flow
- Don't Return Null
- Don't Pass Null
- Using Third Party Code
- Exploring and Learning Boundaries
- Learning Log4J
- Learning Tests are Better than Free
- Using Code that Does Not Yet Exist
- Clean Boundaries
- The Three Laws of TDD
- Keeping Tests Clean
- Domain Specific Testing Language
- One Assert
- Class Organization
- Small Classes
- The Single Responsibility Principles (SRP)
- Maintaining Cohesion
- Organizing for Change
- How would you build a city?
- Separation of Construction and Use
- Dependency Injection
- Scaling Up
- Cross Cutting Concerns
- Test Drive the System Architecture
- Optimize Decision Making
- Use Standards Wisely
- System DSLs
- Getting Clean via Emergent Design
- Simple Design Rules
- DRY (again)
- Minimal Classes and Methods
- Why Concurrency?
- Concurrency Defence Principles
- Know your Library
- Execution Models
- Dining Philosophers
- Beware Dependencies between Synchronized Methods
- Keep Synchronized Sections Small
- Writing Correct Shut-down Code is Hard
- Testing Threaded Code
Smells and Heuristics
- Dozens and dozens of them.
If you are a Java/C#/C++ developer and want to improve your ability to contribute to your team and company by writing better code, this Clean Code course is for you!
To benefit from this Clean Code course, you will need to know Java, C# or C++ prior to attending.
Bring your own hardware
Delegates are required to bring their own laptop to this course as Skills Matter does not provide this.
All delegates will need to have their own laptop with the following:
- Preferred IDE
- 2GB ram