Clean Code Learning Program


Reduce the cost of change and maintenance with Clean Code

Master the art of writing code that’s easy to read, understand, and maintain by using the Clean Code principles compiled by Robert C. Martin (Uncle Bob).

Attending this learning program you will benefit from the trainer’s practical experience with the system of various sizes and in different languages. You will understand how to apply those principles in your code starting the day after the course.

Why Attend

You should attend this learning program if you want to:

  • Write code that is easy to read, understand and change
  • Incrementally clean existing code using the boyscout rule
  • Start using naming principles so you can communicate with your development team through code
  • Learn how to structure methods in classes
  • Reduce the cost of change for your software products

Who Should Attend

  • Mid-level and Senior Programmers
  • Technical Leads looking for improved coding guidelines or improved ways to structure code
  • CTOs who want to reduce the cost of change for their applications

Practical Details

  • Language: English
  • Experiential, hands-on, interactive online learning with practical examples
  • Participants will be awarded a Mozaic Works certificate of completion
Quantity:
- +

Agenda

Clean Code Fundamentals

  • Why is clean code needed? The reasons and benefits for using the clean code principles

Naming

  • Naming Principles; The continuum of names
  • Naming rules for clean code
  • Classification of Names
  • Heuristics for Naming
  • Picking names from domain
  • Common Questions

Functions

  • Functions Principles: small, low indentation, single responsibility, shortlist of arguments, no side effects, error handling is one thing
  • Why use functions?
  • Function guidelines for clean code
  • Review Functions using Clean Code Rules
  • Single Responsibility Principle in Practice
  • General Function Principles

Classes

  • Structuring classes: Small, single responsibility, easy to change
  • Why use classes?
  • Clean Code Guidelines for Classes
  • General principles for classes
  • Types of Classes

Clean Code and Software Design

  • Clean Code and Design
  • Clean Code and Coupling
  • Clean Code and Cohesion
  • Clean Code and SOLID Principles
  • Comments vs. self-explaining code
  • Structuring objects and data
  • The boy scout rule: try and leave the code a little better than you found it

What’s Next?

More details and full agenda here.

Prerequisites

You must be proficient in one of Java, C#, C++, PHP or JavaScript.

Basic knowledge of design patterns and SOLID principles is useful for understanding some of the concepts, but not required.

Meet Your Trainers

0
    0
    Your Cart
    Your cart is empty
      Apply Coupon
      Scroll to Top