ThinkJots

It is important to keep your code organized. (culprits: bad names, not grouping related code, leaky responsibility, bloated interfaces and functions)

Example One: (Pending...)

Small file where imports, class methods, properties are not grouped by relation.

Not so bad, but completely unaware of responsibilities.

Example Two: (Pending...)

Small file has grown.

What?

Example Three: (Pending...)

Refactoring... all the decisions need to be made now. And untangling leaky responsibilities is sad.

Example Four: (Pending...)

Small file, clearly grouped by responsibility.

Example Five: (Pending...)

Refactoring large file, grouped by responsibility.