µObjects

µObjects (micro-objects) introduce a paradigm shift in how to write maintainable Object Oriented code that is highly resistant to code rot.
µObjects 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; µObjects' benefits will be discussed and examples of refactoring into µObjects will be demonstrated.

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


Demonstrations


All Posts

µObjects is still being refined and written about. As I get more bits written I'll be updating some of the "Why?" section links. Easy access to all of the posts involving µObjects and examples is through this here => All µObject posts