Little dudes notation (v. 0.1.0)

This notation reflects particular traits of your object-oriented code as little drawn dudes. As a result, codebase can be represented visually, and badness of bad decisions becomes visual and obvious.

Foundation

1. Dudes - objects
2. Arms (or any other limbs) - methods
3. Tube-fingers - parameters
4. Shake/touch object's hand - call corresponding method
5. "@"-symbols in the brain - instance variables
6. "Internal" hands - private methods
7. Swallen hands - too much conditional logic
8. Legs - same as hands (can be used to reflect "getter" methods)
9. Spawning platforms - classes

Examples

class Book
  attr_reader :title, :author
  def initialize(title, author)
    @title  = title
    @author = author
  end
end

Usage

• exploring other developers' code
• exlaining tricky concepts
• use it as a compact way to reflect code complexity
• visualize "bigger picture" in real projects
• see how things change in dynamics

Learn More

Presentation "Solving Architectural Problems with OOP in Pictures"

Flexibility

You don't have to visualize every single aspect of your class. For example, if for your task instance variables or private methods are not important, you simply don't draw them.

The same goes for classes/objects you want to reflect. For example, when you work on a feature or refactor a part of your code, you might be interested to visualize only a subset of classes.

Extensibility

1. You can use colors to identify classes from different layers of abstractions, or classes of specific namespace.

2. Code coverage, code performance (Big-O notation), churn rate, vulnerabilities, any code complexity metrics can be easily reflected on bodies of the dudes.

Limitations

It was developed for Ruby language, but it can be modified to reflect rules of other Languages. For example, for statically typed languages "tube-fingers" would have different shapes, and only accept arguments of the same shape.