MicroObjects (originally µObjects) introduce a paradigm shift in how to write maintainable Object Oriented code that is highly resistant to code rot.
MicroObjects help your code be more maintainable through many best practices being inescapable. A couple of these are that objects become inherently thread safe and emergent design and evolutionary architecture is unavoidable.

Through the information presented; MicroObjects' benefits will be discussed and examples of refactoring into MicroObjects will be demonstrated.

Driving principle

Have a representation for every concept that exist in the code.

Part 1 - Part 2 - Part 3 - Part 4

The Technical Practices of MicroObjects

  • No Getters (or Setters)
  • Be immutable
  • Interface for Behavior Contracts
  • Abstract 3rd Party Code
  • No Public Statics
  • If Only as a Guard Clause
  • Switch and Else are always evile
  • No Nulls
  • No new inline
  • Extract Cohesion
  • Composition over Inheritance
  • No primitives
  • No enums
  • No logic in constructors

Why?


CLEAN Code