single responsibility principle – Today's Card

Don’t be afraid to add more classes.

You won’t run out of paper.

Code that changes together should reside close together.

Finding code shouldn’t require a search party.

Create simpler triggers.

Keep your logic outside of the trigger.

Learn the Single Responsibility Principle.

That thing should have one job.

The Law of Demeter

Chaining a series of methods together can increase dependencies on distant objects.

Don’t use conjunctions in method names.

Two great ideas taste great together, but not in a method.

Don’t create God classes.

These monsters try to do too much.

An object should not have more than one trigger.

The trigger should have one job.